_ registry / mcp http-sse · checked 2h ago

trust-history-oracle

https://trust-history-oracle.delicate-yellowhorn.workers.dev

Registry code: 25abcb885026502a

api record

Inspect npm package creation, releases, maintainers, and lifecycle-script chronology for dependency trust and AI-agent supply-chain screening.

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

endpoint
https://trust-history-oracle.delicate-yellowhorn.workers.dev/mcp
protocol
http-sse ·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 trust-history-oracle live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is trust-history-oracle free to use?
Yes — the hub reached it with no key and no payment.
What tools does trust-history-oracle have?
5 tools: check_package_instruction_chronology, inspect_npm_package_history, inspect_exact_url_history, sample_package_history, service_info.
Is trust-history-oracle 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
100%

90 days 99.7%· all time 99.7%

latency
616ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 295 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
developer tools code & repositories
used for
  • check package instruction chronology
  • inspect url history
  • inspect npm package history
  • get service information
takes → gives
text, payments → data
tools
5 reads
note
demo or test
_ 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 5 tools
2 open 3 never probed 2 of 5 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.

  • sample_package_history reads open 20h ago

    Free: return a static, clearly labeled example showing the report shape. It performs no live lookup and must not be used as evidence.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • service_info reads open 9h ago

    Free: describe the service, current testnet mode, available evidence tools, prices, and limitations without querying an evidence source.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • check_package_instruction_chronology reads unknown 20h ago

    Paid testnet tool ($0.01 test USDC): compare an archived public instruction with npm registration time and surface deterministic chronology anomalies.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name",
    "instruction_url"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "Exact npm package name."
    },
    "instruction_url": {
      "type": "string",
      "format": "uri",
      "maxLength": 2048,
      "description": "Public documentation URL that may reference the package."
    }
  }
}
    arguments 22 lines
  • inspect_npm_package_history reads unknown 20h ago

    Paid testnet tool ($0.001 test USDC): inspect npm creation, release, maintainer, and lifecycle-script chronology. Returns historical evidence, not a safety guarantee.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 214,
      "minLength": 1,
      "description": "Exact npm package name, including scope when applicable."
    }
  }
}
    arguments 15 lines
  • inspect_exact_url_history reads unknown 9h ago

    Paid testnet tool ($0.002 test USDC): check bounded exact-URL observations in Common Crawl for public-web provenance. Absence cannot be proven.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri",
      "maxLength": 2048,
      "description": "Exact absolute public http(s) URL."
    }
  }
}
    arguments 15 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 25abcb885026502a.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/25abcb885026502a/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/25abcb885026502a/badge.svg)](https://brick.blue/agent/25abcb885026502a?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
90%

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.