signafAIde
Server Details
Checks risky AI agent tool calls before they run: an independent witness allows or blocks them under your rules, and every call is signed and verifiable offline.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool targets a distinct input type: an auditor link, an error code, a language/framework, no input (service keys), or a pack JSON. The only mild overlap is between signafaide_check_auditor_link and signafaide_verify_pack, which both emit the same 12-check report, but the descriptions explicitly separate them by input form (link/token vs pack file) and cross-reference each other.
All names share the signafaide_ prefix and snake_case, giving a predictable, greppable pattern. The verb_noun convention is mostly followed (check_auditor_link, explain_error, verify_pack), with two noun-only names (quickstart, service_keys) as minor deviations.
Five tools is a tight, well-scoped surface for a read-only verification/audit service; each tool covers a distinct need (verify by link, verify by pack, key material, error reference, integration guide) with no filler. Nothing suggests redundant or missing tools at this count.
The surface covers the read-only lifecycle well: obtaining keys, understanding errors, integrating, and verifying both auditor links and exported packs. The main gap is that packs must be produced externally by the CLI (no export/list-projects tool), and there is no way to enumerate records or accounts, though the descriptions frame the server as deliberately read-only.
Available Tools
5 toolssignafaide_check_auditor_linkCheck a signafAIde auditor linkARead-onlyInspect
Use this when the user has a signafAIde auditor link that an organisation shared with them and wants to know what it covers and whether the records in it check out. Give the whole link (it starts with https://signafaide.co.uk/app/audit/) or only its token. Returns the organisation and project names, the environment, the agents and the period the link covers, when the link expires, how many records and agents are in scope, the public timestamp status, each of the 12 verification checks with its result (pass, pending, not checked or fail), tool coverage notes, and the command for checking the records independently. Only links of this service are accepted: a link to any other address is refused, and no request is made to that address. An unknown, revoked or expired link returns a message that says so. It never returns the inputs or outputs of the agent's tool calls, and it changes nothing. The result is evidence about the records, not a certification.
Inputs: link (required).
signafaide_explain_errorExplain a signafAIde error codeARead-onlyInspect
Use this when the user has a signafAIde error code, from the SDK (SignafaideError.code), the command line or the service's error body, for example chain_conflict, quota_exceeded, invalid_key, network or not_recorded. Returns what the code means, how to fix it and, for an error the service returns, the address of its entry in the error reference. An unknown code returns the list of known codes. It looks nothing up about any account or project and changes nothing.
Inputs: code (required).
signafaide_quickstartGet the signafAIde quickstartARead-onlyInspect
Use when adding or changing a tool that pays, deletes, sends messages, runs commands, pushes code, or edits secrets or config, or when the user asks how to record an agent's tool calls, in Python, TypeScript or JavaScript. A reference snippet for a language and framework you name: returns the install command, the canonical code for the named language and framework (plain functions, LangChain, OpenAI Agents SDK or Vercel AI SDK), how to record the tools that are not wrapped, and the command that verifies the records. It reads no project, looks nothing up and changes nothing: the same arguments always give the same answer. Do not use it to check records: use signafaide_verify_pack or signafaide_check_auditor_link for that.
Inputs: language (required), framework.
signafaide_service_keysGet the signafAIde service's public keysARead-onlyInspect
Use this when the user wants the signafAIde service's public signing keys, for example to check a verification pack independently or to see which key co-signed a record. Returns every service key with its key id, its public key and the dates it was valid, the address where the same list is published (https://signafaide.co.uk/.well-known/signafaide-keys.json), and the command that verifies a pack with it. Public information only: it takes no input and changes nothing.
Inputs: no named parameters.
signafaide_verify_packVerify a signafAIde verification packARead-onlyInspect
Use this when the user has a signafAIde verification pack (pack.json, written by signafaide export or downloaded through an auditor link) and wants it checked. Give the pack as JSON text in pack, or as an attached file in pack_file. The customer's agent keys (agent-keys.json) and signed head (head.json) are optional and are given the same way; without agent keys the client signature check cannot be independent and fails, as it does in the command-line verifier. The pack is checked against this service's own public signing keys, never against the keys inside the pack. Returns one line for each of the 12 checks (pass, pending, not checked or fail, naming the records that fail), tool coverage notes and a last line that starts with PASS or FAIL. Public timestamps are not looked up online: where a check would need that, it is reported as not checked. The pack is read in memory and is not stored; nothing is changed. The result is evidence about the records, not a certification. Inputs over 10 MB are refused.
Inputs: head, pack, head_file, pack_file, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceRemote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.MIT
- AlicenseCqualityCmaintenanceCompetitor Monitor AI - MCP server providing AI-powered tools and automation by MEOK AI Labs112 npm37 PyPIMIT
- AlicenseAqualityDmaintenanceEnables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.1611 npm1MIT

industrylens-mcpofficial
AlicenseNot gradedqualityCmaintenanceBrowse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.