pulsemcp/agentstamp · v2.3.0
As of 2026-10-16 15:19 UTC, AgentStamp is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95.9% of Glimind's liveness checks. It had 154 outages in 90 days, with a median recovery of 7 minutes.
Identity certification, public registry, reputation scoring, and x402 micropayments for AI agents built on Base and Solana.
Point your MCP client at this streamable_http endpoint: https://agentstamp.org/mcp
The endpoint did not complete an MCP handshake.
Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST.
19 of 19 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones.
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call.
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Reachable 95.9% of the time over the last 30 days; median recovery 7 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,208 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/pulsemcp%2Fagentstamp/fixes
{
"name": "bridge_erc8004_lookup",
"description": "Look up an ERC-8004 on-chain agent and get their AgentStamp trust score. Free. Returns on-chain identity + trust verdict.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"erc8004_agent_id"
],
"properties": {
"erc8004_agent_id": {
"type": "string",
"pattern": "^\\d+$",
"description": "ERC-8004 agent ID (numeric token ID from the Identity Registry)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "bridge_erc8004_trust_check",
"description": "Get an AgentStamp trust verdict for an ERC-8004 agent. Free. Returns trusted/untrusted with score.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"erc8004_agent_id"
],
"properties": {
"erc8004_agent_id": {
"type": "string",
"pattern": "^\\d+$",
"description": "ERC-8004 agent ID (numeric token ID)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "browse_agents",
"description": "Browse registered agents with optional category filter and sorting.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"sort": {
"enum": [
"endorsements",
"newest",
"name",
"reputation"
],
"type": "string",
"default": "endorsements",
"description": "Sort order"
},
"limit": {
"type": "integer",
"default": 10,
"maximum": 100,
"minimum": 1,
"description": "Max results (1-100)"
},
"category": {
"type": "string",
"description": "Filter by category"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["pulsemcp/agentstamp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "pulsemcp/agentstamp"}) over MCP.
create_team ~189 tokenssearch_agents ~170 tokensbrowse_agents ~148 tokenstrust_check ~133 tokensteam_trust_check ~132 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/pulsemcp%2Fagentstamp?ref=badge)
<a href="https://glimind.com/server/pulsemcp%2Fagentstamp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/pulsemcp%2Fagentstamp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/pulsemcp%2Fagentstamp.svg :target: https://glimind.com/server/pulsemcp%2Fagentstamp?ref=badge :alt: MCP agent-readiness
Compare: most reliable blockchain servers · most reliable search servers · most reliable compliance servers · most reliable communication servers · most reliable web servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-16 15:19 UTC, AgentStamp is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 95.9% of Glimind's liveness checks. It had 154 outages in 90 days, with a median recovery of 7 minutes.
AgentStamp advertises 19 tools, including bridge_erc8004_lookup, bridge_erc8004_trust_check, browse_agents, browse_wishes, compliance_report.
Point your MCP client at this streamable_http endpoint: https://agentstamp.org/mcp
Glimind scanned all 19 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.