Attest runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 25 Sep 2026.
Decide by policy, gate behind a human, verify by read-back, record a hash-chained ledger.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
subprocess.run(["git", "-C", str(self.repo), "add", str(f.relative_to(self.repo))], check=True, capture_output=True)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to Attest
same job, measured the same wayZero-code proxy: policy, human gate, read-back and a hash-chained ledger for any MCP server.
Hash-chained audit ledger for AI agent work — record, verify and replay what the agent did.
Read-only facts about Grideōs from its signed, hash-chained ledger. Verify before you cite.
Attest agent decisions and verify records on a public ledger. Evidence, not just data.
Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
Negotiate for your human under PXP: tagged claims, escalation, decision brief, hash-chained ledger
Fail-closed quality gate and hash-chained receipt ledger for AI agent workflows.
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
Attest — questions
Answers built from our own checks of this server.