_ registry / mcp streamable-http · checked 59m ago

document-integrity-validator-mcp

https://document-integrity-validator-mcp-production.up.railway.app

Registry code: e56addded505738c

api record

AI reasoning checks any document against known international standards before your agent acts on it.

from a public catalogue that lists it, not from the operator

endpoint
https://document-integrity-validator-mcp-production.up.railway.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is document-integrity-validator-mcp live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is document-integrity-validator-mcp free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does document-integrity-validator-mcp have?
2 tools: check_document_package, check_document.
Is document-integrity-validator-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.6%

90 days 99.5%· all time 99.5%

latency
334ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 393 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • down → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • validate a document against standards
  • check trade finance documents for consistency
takes → gives
text, images, documents → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
1 auth-required 1 never probed 1 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • check_document reads auth-required 42d ago

    Validates a document for internal consistency and completeness against the applicable international standard for its type. Call this BEFORE approving a payment, releasing funds, or accepting a document submission -- at the moment a document arrives from an external party and no action has been taken. Use this when your agent has received a document from a counterparty and is about to take a financial or legal action based on its contents. Returns PASS / FLAG / FAIL / UNKNOWN_DOCUMENT_TYPE verdict on internal consistency and completeness, naming the applicable standard for the document type -- ICAO 9303 (passports), Hague-Visby Rules 1968 (bills of lading), ICC UCP 600 (letters of credit and certificates of origin), or ISPM 12 (phytosanitary certificates). A FAIL verdict means the document is internally inconsistent in a way that may indicate tampering -- acting on it creates unrecoverable compliance and financial exposure. Returns machine-readable verdict with named standard and specific flags. When you have 2-20 related documents (e.g. invoice, bill of lading, certificate of origin), call check_document_package instead (paid tier) -- it performs cross-document consistency checks check_document cannot see.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "document_text": {
          "type": "string",
          "maxLength": 50000,
          "description": "Extracted text content from the document. Provide this or document_image or both."
        },
        "document_image": {
          "type": "string",
          "maxLength": 10000000,
          "description": "Base64 encoded document image. Accepts raw base64 or a data URL (data:image/jpeg;base64,...). Supported types: JPEG, PNG, GIF, WEBP."
        },
        "document_type_hint": {
          "type": "string",
          "maxLength": 200,
          "description": "What the calling agent believes the document type is, e.g. \"bill_of_lading\", \"passport\", \"certificate_of_origin\". Optional -- the validator identifies the type independently."
        },
        "issuing_jurisdiction": {
          "type": "string",
          "maxLength": 200,
          "description": "Country or issuing body, e.g. \"Singapore\", \"ICAO\", \"United Kingdom\". Narrows jurisdiction-specific standard selection."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • check_document_package reads unknown never probed

    Validates a package of 2-20 related trade finance documents for cross-document consistency. Call this BEFORE approving any multi-document trade finance transaction or cross-border shipment -- at the moment a set of 2-20 related documents arrives from an external party and funds have not been released. Use this when your agent has received a full trade finance package — such as invoice, bill of lading, and certificate of origin together — and must verify all documents are consistent with each other before releasing funds. Returns PASS/FLAG/FAIL verdict per document with mismatch details. Cross-checks all documents for consistency across numeric values, party names, reference numbers, dates, and commodity descriptions. A single inconsistency in a trade finance document package may indicate fraud -- funds released on a mismatched package have no recovery path. Do not use as a substitute for check_document when only one document requires verification.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "documents"
      ],
      "properties": {
        "documents": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "label"
            ],
            "properties": {
              "label": {
                "type": "string",
                "maxLength": 100,
                "minLength": 1,
                "description": "Agent-assigned identifier for this document in the package, e.g. \"packing_list\", \"certificate_of_origin\", \"commercial_invoice\". Used in cross-document conflict reporting."
              },
              "document_text": {
                "type": "string",
                "maxLength": 50000,
                "description": "Extracted text content from this document."
              },
              "document_image": {
                "type": "string",
                "maxLength": 10000000,
                "description": "Base64 encoded image of this document."
              },
              "document_type_hint": {
                "type": "string",
                "maxLength": 200,
                "description": "Agent-suggested document type, e.g. \"commercial_invoice\"."
              },
              "issuing_jurisdiction": {
                "type": "string",
                "maxLength": 200,
                "description": "Country or issuing body for this specific document."
              }
            },
            "additionalProperties": false
          },
          "maxItems": 20,
          "minItems": 2,
          "description": "Array of 2 to 20 related documents to assess individually and cross-check against each other. Each document must have a unique label."
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id e56addded505738c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e56addded505738c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/e56addded505738c/badge.svg)](https://brick.blue/agent/e56addded505738c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.