Is the Chriscorp Tracea MCP server down?

mcp-registry/io.github.chriscorp/tracea · v0.1.0

As of 2026-10-18 07:34 UTC, the Chriscorp Tracea MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.

Tracea — legal identity (Know Your Agent) for AI agents, on-chain. ERC-8004 compatible.

claude mcp add --transport http chriscorp-tracea-mcp-server https://mcp.tracea.online/mcp

{
  "mcpServers": {
    "chriscorp-tracea-mcp-server": {
      "type": "http",
      "url": "https://mcp.tracea.online/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

What to fix (4)

Auto-fix: 12 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.chriscorp%2Ftracea/fixes

{
  "name": "check_payment_allowed",
  "description": "Dry-run a payment BEFORE executing it: checks on-chain whether the agent's smart account would allow it (permission granted, within financial cap, destination approved if a whitelist exists). Returns { allowed, reason }.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "agent_address",
      "destination",
      "amount_eth"
    ],
    "properties": {
      "amount_eth": {
        "type": "string",
        "description": "Amount in ETH, e.g. '0.001'"
      },
      "destination": {
        "type": "string",
        "description": "Destination address to pay"
      },
      "agent_address": {
        "type": "string",
        "description": "Ethereum address of the agent (its smart account address)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_action",
  "description": "Read a single logged agent action from the Tracea ActionLog contract by its numeric ID. Returns agent, action type, payload and timestamp.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "action_id"
    ],
    "properties": {
      "action_id": {
        "type": "integer",
        "maximum": 9007199254740991,
        "minimum": 0,
        "description": "Numeric action ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_agent_actions",
  "description": "List all on-chain action IDs logged for a given agent on Tracea.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "agent_address"
    ],
    "properties": {
      "agent_address": {
        "type": "string",
        "description": "Ethereum address of the agent"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

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":["mcp-registry/io.github.chriscorp/tracea"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.chriscorp/tracea"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~2,389 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.65% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• report_activity ~363 tokens
• payment_required ~297 tokens
• payment_incoming ~192 tokens
• check_payment_allowed ~190 tokens
• log_action ~184 tokens

Static 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:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chriscorp%2Ftracea.svg)](https://glimind.com/server/mcp-registry%2Fio.github.chriscorp%2Ftracea?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fio.github.chriscorp%2Ftracea?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chriscorp%2Ftracea.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.chriscorp%2Ftracea.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.chriscorp%2Ftracea?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:82a14c8c1b3d09c6…, first seen 2026-10-17, included at leaf 4501 of 20,870. Version history · verify what your client received.

Tools (15)

• check_payment_allowed
• get_action
• get_agent_actions
• get_agent_info
• get_my_identity
• get_owner_agents
• get_payment_whitelist
• get_registration_file
• is_agent_revoked
• log_action
• payment_incoming
• payment_required
• payment_status
• report_activity
• verify_agent

Compare: most reliable finance servers · most reliable data servers · most reliable retrieval servers · most reliable security servers · most reliable knowledge servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Chriscorp Tracea MCP server down right now?

As of 2026-10-18 07:34 UTC, the Chriscorp Tracea MCP server is up with a Glimind reliability score of 80/100 (grade B). Over the last 30 days it answered 99.6% of Glimind's liveness checks. It had 11 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Chriscorp Tracea MCP server provide?

Chriscorp Tracea MCP server advertises 15 tools, including check_payment_allowed, get_action, get_agent_actions, get_agent_info, get_my_identity.

How do I install Chriscorp Tracea MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.tracea.online/mcp

Is the Chriscorp Tracea MCP server safe to connect to an AI agent?

Glimind scanned all 15 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.

Operator of Chriscorp Tracea MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

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. Maintainers: alerts, deploy attestation and monthly reports.

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.