Pacta MCP server
io.github.Fractal-Neurons/pactaFractal-Neuronsstreamable-httpv0.1.5Scanned
Free pre-execution contract checks for AI agents: preflight, control-plane scans, EAS anchors.
7 tools: 4 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
4 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Pacta MCP server can do
The Pacta MCP server is published by the GitHub account Fractal-Neurons. It has 7 tools. It can create or change data (4 tools: pacta_check_preflight, pacta_scan_control_plane, pacta_scan_timelock_op and pacta_submit_request), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (pacta_lookup_protocol and pacta_get_live_timelocks).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.1.5.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Changes things 4Claude Code: ask
pacta_check_preflightOne-call pre-execution safety check of a contract before an agent interacts with it: verdict (immutable / timelock / zero-delay timelock / multisig / EOA admin / unclassified / und…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it One-call pre-execution safety check of a contract before an agent interacts with it: verdict (immutable / timelock / zero-delay timelock / multisig / EOA admin / unclassified / undeployed), 0-100 risk score, proxy + implementation, controller kind, zero-delay upgradeability and pause / blacklist / upgrade capabilities, pinned to a block. Free during the launch (no key, no payment).
Annotations the server declares
- title: Pre-execution safety check
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pacta_scan_control_planeLive control-plane scan of an EVM contract: EIP-1967 implementation/admin/beacon, owner(), Safe threshold/owners/guard, timelock delay, code size and deterministic risk flags at th…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Live control-plane scan of an EVM contract: EIP-1967 implementation/admin/beacon, owner(), Safe threshold/owners/guard, timelock delay, code size and deterministic risk flags at the latest (or a given) block. Free during the launch (no key, no payment).
Annotations the server declares
- title: Control-plane scan
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pacta_scan_timelock_opLive OpenZeppelin TimelockController operation state: isOperation/Pending/Ready/Done, getTimestamp (ETA), getMinDelay at the latest block.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Live OpenZeppelin TimelockController operation state: isOperation/Pending/Ready/Done, getTimestamp (ETA), getMinDelay at the latest block. Free during the launch (no key, no payment).
Annotations the server declares
- title: Timelock operation state
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pacta_submit_requestOpt-in: queue a coverage or feature request with Pacta when a target is not indexed, a chain or check is unsupported, or data looks wrong (coverage_gap_hint).No findings
Why it is in this group
- The name "pacta_submit_request" says "submit": a word for a change.
Description, as the server wrote it Opt-in: queue a coverage or feature request with Pacta when a target is not indexed, a chain or check is unsupported, or data looks wrong (coverage_gap_hint). Ask the user first. Free in every pricing mode, 5 per hour; an identical request_type + target_subject upvotes the existing request (same request_id). Returns request_id, status, demand_votes and an optional fast_track_url. Never opens a GitHub issue. Pass contact_handle ONLY when the user explicitly asks for follow-up or an invoice.
Annotations the server declares
- title: Submit Pacta Coverage or Feature Request
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
pacta_get_live_timelocksLive state of the public pending timelock operations tracked in https://pacta.wtf/api/v1/radar.json, each re-checked at the latest block (getTimestamp, isOperationPending, isOperat…Reads text others writeNo findings
Why it is in this group
- The name "pacta_get_live_timelocks" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Live state of the public pending timelock operations tracked in https://pacta.wtf/api/v1/radar.json, each re-checked at the latest block (getTimestamp, isOperationPending, isOperationDone). Free during the launch (no key, no payment).
Annotations the server declares
- title: Live tracked timelock operations
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pacta_lookup_protocolResolve a protocol or token name to Pacta's verified record: canonical slug and page URL, checksummed primary contract and controller, classification with its evidence basis (Base-…Reads text others writeNo findings
Why it is in this group
- The name "pacta_lookup_protocol" says "lookup": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "resolve" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it Resolve a protocol or token name to Pacta's verified record: canonical slug and page URL, checksummed primary contract and controller, classification with its evidence basis (Base-EAS-attested vs RPC-observed only), and ready-to-use preflightArgs {chain, address} for pacta_check_preflight. 70 protocols + 8 briefs, answered in memory (no RPC). Free in every pricing mode.
Annotations the server declares
- title: Lookup Protocol or Token by Name
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
pacta_scan_proposal_diffRe-runs the pinned contract reads of a Pacta-tracked governance proposal (Aave, Euler, Morpho, Sky) at the live block and returns pinned-vs-live diffs.No findings
Why it is in this group
- The name "pacta_scan_proposal_diff" says "diff": a word for reading.
Description, as the server wrote it Re-runs the pinned contract reads of a Pacta-tracked governance proposal (Aave, Euler, Morpho, Sky) at the live block and returns pinned-vs-live diffs. Free during the launch (no key, no payment).
Annotations the server declares
- title: Governance proposal pinned-vs-live diff
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:19 UTC, unchanged since Nov 15, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (4 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://pacta-x402.pacta.workers.dev/mcp: tools/list returned 7 tools to an anonymous client, including pacta_check_preflight (write), pacta_scan_control_plane (write), pacta_scan_timelock_op (write), pacta_submit_request (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:pacta_lookup_protocolOnly readsdescriptioninputSchema
Tools2 added, 5 changed.+2 added~5 changedView diff
- Added:pacta_lookup_protocolOnly reads
- Added:pacta_submit_requestChanges things
- Changed:pacta_check_preflightChanges thingsinputSchemaannotations
- Changed:pacta_get_live_timelocksOnly readsinputSchemaannotations
- Changed:pacta_scan_control_planeChanges thingsinputSchemaannotations
- Changed:pacta_scan_proposal_diffOnly readsinputSchemaannotations
- Changed:pacta_scan_timelock_opChanges thingsinputSchemaannotations
Install
Pinned to version 0.1.5. Values in angle brackets are yours to fill in.
claude mcp add --transport http pacta https://pacta-x402.pacta.workers.dev/mcpclaude mcp add --transport http pacta https://pacta-x402.pacta.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__pacta__pacta_lookup_protocol",
"mcp__pacta__pacta_scan_proposal_diff",
"mcp__pacta__pacta_get_live_timelocks"
],
"ask": [
"mcp__pacta__pacta_check_preflight",
"mcp__pacta__pacta_scan_control_plane",
"mcp__pacta__pacta_scan_timelock_op",
"mcp__pacta__pacta_submit_request"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as pacta. Review it before you use it.
Capability tags behind 2 rules
- mcp__pacta__pacta_lookup_protocol untrusted-input
- mcp__pacta__pacta_get_live_timelocks untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Fractal-Neurons/pacta/verify?hash=6d92888dc8762b3b861081bfe8363c327c6e39076ee869df8c620094a8b9aad5" | jq -e '.changed == false'Pinned hash 6d92888dc876, from Nov 16, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Fractal-Neurons/pacta/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Fractal-Neurons/pacta)Source: MCP Registry · repository. Synced Nov 16, 2026, 12:17 UTC.
Pacta MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Pacta MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Pacta MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Pacta MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Pacta MCP server have?
- 7 tools: 4 write, 3 read. pacta_check_preflight, pacta_scan_control_plane, pacta_scan_timelock_op, pacta_submit_request, pacta_lookup_protocol, pacta_scan_proposal_diff and pacta_get_live_timelocks.
Does the Pacta MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Pacta MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Pacta MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.