Signed tool-manifest attestation — fomite MCP Resource
Signed tool-manifest attestation
is one of 6 resources on the
fomite
MCP server. Connect the server and your client can attach it as context.
by client
How to attach Signed tool-manifest attestation from your client
- Claude Code fomite Resource/Signed tool-manifest attestation run in your project directory
- Claude Desktop fomite Resource/Signed tool-manifest attestation ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor fomite Resource/Signed tool-manifest attestation ~/.cursor/mcp.json
- VS Code fomite Resource/Signed tool-manifest attestation .vscode/mcp.json
- Zed fomite Resource/Signed tool-manifest attestation ~/.config/zed/settings.json
- Windsurf fomite Resource/Signed tool-manifest attestation ~/.codeium/windsurf/mcp_config.json
- Cline fomite Resource/Signed tool-manifest attestation ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI fomite Resource/Signed tool-manifest attestation ~/.gemini/settings.json
- Grok fomite Resource/Signed tool-manifest attestation .mcp.json (in your project root)
- ChatGPT fomite Resource/Signed tool-manifest attestation Settings → Connectors → Advanced → Developer mode
- Claude.ai fomite Resource/Signed tool-manifest attestation Settings → Connectors → Add custom connector
- LangChain fomite Resource/Signed tool-manifest attestation pip install langchain-mcp-adapters
Other resources on this server
fomite also offers 3 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 24 September 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.