Is the Jdhart81 Agent Provenance MCP server down?

mcp-registry/io.github.jdhart81/agent-provenance · v1.28.1

As of 2026-10-18 13:40 UTC, the Jdhart81 Agent Provenance MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 3 minutes.

Genesis certificates, lineage, and cascading recalls: birth certificates + bloodlines for the agent

claude mcp add --transport http jdhart81-agent-provenance-mcp-server https://mcp.viridisconservation.com/provenance/mcp

{
  "mcpServers": {
    "jdhart81-agent-provenance-mcp-server": {
      "type": "http",
      "url": "https://mcp.viridisconservation.com/provenance/mcp"
    }
  }
}

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

Agent-readiness: C (76/100)

What to fix (2)

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 10 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.jdhart81%2Fagent-provenance/fixes

{
  "name": "describe_agent",
  "description": "Fleet-standard self-description.",
  "inputSchema": {
    "type": "object",
    "title": "describe_agentArguments",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_artifact",
  "description": "Fetch one registered artifact by artifact_id.",
  "inputSchema": {
    "type": "object",
    "title": "get_artifactArguments",
    "required": [
      "artifact_id"
    ],
    "properties": {
      "artifact_id": {
        "type": "string",
        "title": "Artifact Id"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_certificate",
  "description": "Fetch an agent's genesis certificate + recall/quarantine status.",
  "inputSchema": {
    "type": "object",
    "title": "get_certificateArguments",
    "required": [
      "agent_id"
    ],
    "properties": {
      "agent_id": {
        "type": "string",
        "title": "Agent Id"
      }
    }
  },
  "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.jdhart81/agent-provenance"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.jdhart81/agent-provenance"}) over MCP.

Passed

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

Largest tool definitions

• register_artifact ~237 tokens
• register_genesis ~180 tokens
• recall ~100 tokens
• verify_certificate ~87 tokens
• verify_artifact ~83 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.jdhart81%2Fagent-provenance.svg)](https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-provenance?ref=badge)

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

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jdhart81%2Fagent-provenance.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.jdhart81%2Fagent-provenance?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:fdd29b98b9a790b3…, first seen 2026-10-17, included at leaf 5090 of 22,126. Version history · verify what your client received.

Tools (24)

• agent-arbitration
• agent-compute-ledger
• agent-covenant
• agent-escrow
• agent-identity-registry
• agent-metering
• agent-offset-clearinghouse
• agent-provenance
• agent-trust-oracle
• describe_agent
• get_artifact
• get_certificate
• lineage
• list_artifacts
• list_records
• narrative-engine
• protogen
• recall
• register_artifact
• register_genesis
• regulatory-radar
• smartscale
• verify_artifact
• verify_certificate

Compare: most reliable other servers · most reliable security servers · most reliable finance servers · most reliable knowledge servers · most reliable ml servers

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

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

FAQ

Is the Jdhart81 Agent Provenance MCP server down right now?

As of 2026-10-18 13:40 UTC, the Jdhart81 Agent Provenance MCP server is up with a Glimind reliability score of 92/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 7 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Jdhart81 Agent Provenance MCP server provide?

Jdhart81 Agent Provenance MCP server advertises 24 tools, including agent-arbitration, agent-compute-ledger, agent-covenant, agent-escrow, agent-identity-registry.

How do I install Jdhart81 Agent Provenance MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.viridisconservation.com/provenance/mcp

Is the Jdhart81 Agent Provenance MCP server safe to connect to an AI agent?

Glimind scanned all 11 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 Jdhart81 Agent Provenance 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.