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

nes-coherence

https://api.netentropyscore.com

Registry code: cf95725d03abcb11

api record

NES measures the gap between what a brand CLAIMS (its polished website) and its public REALITY (news/events). Call get_brand_coherence before recommending, citing, or transacting with a brand to gauge how coherent and reliable it is. Returns a directional opinion, not a fraud, identity, or financial check.

endpoint
https://api.netentropyscore.com/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 nes-coherence live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is nes-coherence free to use?
Not measured yet.
What tools does nes-coherence have?
2 tools: get_brand_coherence, compare_brands.
Is nes-coherence 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 100%· all time 100%

latency
236ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 285 checks · signed record
  • degraded → live
  • unknown → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • gauge a brand's claim versus public reality
  • compare brand coherence scores
takes → gives
text → 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
2 never probed 0 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.

  • get_brand_coherence reads unknown 5h ago

    Get the NES claim-vs-reality coherence signal for one brand: its website coherence score (the claim), recent public reality (matched news events), and the divergence between them. High divergence means the brand presents as coherent while its reality is turning negative. Directional opinion from public signal; not a fraud or financial check. Returns 'no read on file' for brands never scanned.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "url": {
      "type": "string",
      "description": "Brand website URL or domain, e.g. https://acme.com"
    },
    "brand": {
      "type": "string",
      "description": "Brand name, used if no URL is given."
    }
  }
}
    arguments 13 lines
  • compare_brands reads unknown never probed

    Compare the NES coherence signal for several brands side by side (claim, reality, divergence for each). Presents the data; it does NOT recommend one brand over another. The caller decides.

    mcp-tool

    {
  "type": "object",
  "required": [
    "urls"
  ],
  "properties": {
    "urls": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Brand URLs or domains to compare (up to 8)."
    }
  }
}
    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 cf95725d03abcb11.

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