Is the Uscodex MCP server down?

mcp-registry/org.uscodex/uscodex · v0.1.0

healthy
Last checked 2026-10-26 13:21 UTC · handshake 131ms

As of 2026-10-26 13:21 UTC, the Uscodex MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 20 minutes.

uptime (30d checks)
99.9%
checks observed
4,870
outages (90d)
2
tools
5

Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.

Install Uscodex MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http uscodex-mcp-server https://uscodex.org/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "uscodex-mcp-server": {
      "type": "http",
      "url": "https://uscodex.org/mcp"
    }
  }
}

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

Agent-readiness: B (85/100)

B (85/100): 0 error(s), 1 warning(s) across 5 tool(s); ~1,308 tokens of tool definitions.
Scores higher than 45% of 15,751 MCP servers Glimind has audited.
Its tool list costs an agent ~1,308 tokens per session — lighter than 65% of servers.
85 → 85 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (2)

5 of 5 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. How to fix →

Tools: citations, compare, fetch, history, search

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. How to fix →

Auto-fix: 3 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%2Forg.uscodex%2Fuscodex/fixes

compare 1 change
{
  "name": "compare",
  "description": "What changed in a code section between two releases: each provision added, removed, changed or renumbered, the edits marked <del> and <ins>. To compare versions of a bill, take the 'what changed' link from its history.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "to": {
        "type": "string",
        "description": "Release point or date to compare to. Defaults to the latest."
      },
      "from": {
        "type": "string",
        "description": "Release point or date to compare from. Defaults to the release before `to`."
      },
      "path": {
        "type": "string",
        "description": "A page of the site, as its path or full URL (\"/usc/26/61\", \"/pl/119/21\"). Give this or `citation`."
      },
      "citation": {
        "type": "string",
        "description": "A citation (\"26 U.S.C. 61(a)\", \"40 CFR 60.1\", \"Pub. L. 119-21\", \"H.R. 1\", \"E.O. 14000\"). Give this or `path`."
      },
      "only_edits": {
        "type": "boolean",
        "default": true,
        "description": "Only the provisions that changed, not the whole text."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
fetch 1 change
{
  "name": "fetch",
  "description": "Read a document or page of the site as markdown: a code section with its notes, a title's or unit's contents, a public law, a bill (at any version), an executive order. Paths also reach the corpus indexes (\"/usc\", \"/pl?congress=118\", \"/bills?congress=119\", \"/eo\") and each code's releases (\"/usc/releases\"). Links in the markdown are paths this tool accepts.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "path": {
        "type": "string",
        "description": "A page of the site, as its path or full URL (\"/usc/26/61\", \"/pl/119/21\"). Give this or `citation`."
      },
      "notes": {
        "type": "boolean",
        "default": true,
        "description": "Include a section's source credit, notes and footnotes."
      },
      "release": {
        "type": "string",
        "description": "For a code, the release to read it at: a release point (\"119-21\") or a date (YYYY-MM-DD) for the release in force then. Defaults to the latest."
      },
      "citation": {
        "type": "string",
        "description": "A citation (\"26 U.S.C. 61(a)\", \"40 CFR 60.1\", \"Pub. L. 119-21\", \"H.R. 1\", \"E.O. 14000\"). Give this or `path`."
      },
      "provision": {
        "type": "string",
        "description": "Part of the document: in a code section, a provision and everything under it (\"a-1\" for (a)(1)) or a run of them (\"a..c\"); in a law, bill or order, a heading's {#anchor} (\"tI-stA-s10101\") or a provision under it (\"tI-stA-s10101-a\")."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
search 1 change
{
  "name": "search",
  "description": "Search the full text of federal law: United States Code, Code of Federal Regulations, Public Laws, Congressional Bills, Executive Orders. Results are ranked across every corpus unless `corpus` narrows them, each with its citation, a link and the matching words. A query that is only a citation returns that document instead.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "date": {
        "type": "string",
        "description": "For a code, search it as it stood on this date (YYYY-MM-DD)."
      },
      "page": {
        "type": "integer",
        "default": 1,
        "description": "Page of results, 20 to a page."
      },
      "query": {
        "type": "string",
        "description": "Words, a \"quoted phrase\", NOT before a word to exclude it, or a citation."
      },
      "title": {
        "type": "string",
        "description": "For a code, search one title (\"11\", \"40\")."
      },
      "corpus": {
        "enum": [
          "usc",
          "cfr",
          "pl",
          "bills",
          "eo"
        ],
        "type": "string",
        "description": "Search one corpus only."
      }
    }
  },
  "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/org.uscodex/uscodex"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/org.uscodex/uscodex"}) over MCP.

Passed

Largest tool definitions

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:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.uscodex%2Fuscodex.svg)](https://glimind.com/server/mcp-registry%2Forg.uscodex%2Fuscodex?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Forg.uscodex%2Fuscodex?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.uscodex%2Fuscodex.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Forg.uscodex%2Fuscodex.svg
   :target: https://glimind.com/server/mcp-registry%2Forg.uscodex%2Fuscodex?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:255d008d6395fcc5…, first seen 2026-10-17, included at leaf 5835 of 73,100. Version history · verify what your client received.

Tools (5)

Compare: most reliable search servers · most reliable data servers · most reliable retrieval servers · most reliable knowledge servers

Know before your agent calls it

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.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

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"
    }
  }
}

FAQ

Is the Uscodex MCP server down right now?

As of 2026-10-26 13:21 UTC, the Uscodex MCP server is up with a Glimind reliability score of 88/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 20 minutes.

How many tools does Uscodex MCP server provide?

Uscodex MCP server advertises 5 tools, including citations, compare, fetch, history, search.

How do I install Uscodex MCP server?

Point your MCP client at this streamable-http endpoint: https://uscodex.org/mcp

Is the Uscodex MCP server safe to connect to an AI agent?

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

Feedback
Help us improve