verity-mcp
Registry code: aa69e2c3c05486eb
Real-time social media and prediction market integrity layer for traders, funds, and quant desks.
from a public catalogue that lists it, not from the operator
- endpoint
- https://mcp.verityskills.com/sse
- protocol
- streamable-http ·2025-03-26
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is verity-mcp live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is verity-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 verity-mcp have?
- 7 tools: verity-scan, coordination-heat, morning-brief, verity-score, disinfo-alert, notification-prefs, cross-check-alert.
- Is verity-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.
90 days 99.7%· all time 99.7%
last good check
of 7 tools
- degraded → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- finance & markets
- used for
- score a ticker for coordinated social activity
- check a claim against sources
- get a daily watchlist brief
- scan for disinformation
- takes → gives
- text → data
- tools
- 6 reads1 changes data
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.
through this hub
successful
what callers paid
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.
cross-check-alert reads auth-required 26h ago
Cross-reference a claim against monitored sources and flag inconsistencies. Returns matched citations, cross-source conflicts, and a confidence verdict (CORROBORATED, CONFLICTED, UNVERIFIED, or NO_SIGNAL) suitable for a compliance trail.
{ "type": "object", "required": [ "claim" ], "properties": { "claim": { "type": "string", "maxLength": 500, "description": "A specific testable statement to verify. Example: \"BlackRock filed for a spot Solana ETF on 2026-03-12\"." }, "sources": { "type": "array", "items": { "type": "string" }, "maxItems": 20, "description": "Optional preferred sources to weight higher. Pass canonical domains, like reuters.com or sec.gov." } }, "additionalProperties": false }arguments 22 linesverity-scan reads unknown never probed
Real-time scan of a topic, ticker, or claim. Returns a structured verdict an agent can use as a pre-trade check before any significant position. The trade does not fire until the scan clears it.
{ "type": "object", "required": [ "subject" ], "properties": { "subject": { "type": "string", "description": "Ticker symbol, topic phrase, or short claim to scan. Examples: AAPL, \"Fed pause priced in\", \"OPEC cut announcement\"." } }, "additionalProperties": false }arguments 13 linescoordination-heat reads unknown never probed
Score a topic, ticker, or narrative for coordinated activity across public social platforms. Distinguishes organic chatter from manufactured campaigns: identical phrasing across many posts, new-account clusters, synchronized posting windows. Returns a heat score with a band and the contributing signal counts.
{ "type": "object", "required": [ "subject" ], "properties": { "subject": { "type": "string", "description": "Ticker symbol, topic phrase, or named narrative to score. Examples: GME, \"AI energy demand\", \"Iran ceasefire\"." } }, "additionalProperties": false }arguments 13 linesmorning-brief reads unknown never probed
Daily briefing of overnight signals across a watchlist. Aggregates coordination shifts, narrative changes, and integrity flags into one structured report ready to drop into a morning prep workflow.
{ "type": "object", "required": [ "watchlist" ], "properties": { "watchlist": { "type": "array", "items": { "type": "string" }, "maxItems": 50, "minItems": 1, "description": "Tickers or topic phrases to brief on. Required: a non-empty list." } }, "additionalProperties": false }arguments 18 linesverity-score reads unknown never probed
Composite integrity score for a market subject. Returns a 0 to 100 score with contributing factor weights so an analyst can decide whether a thesis is grounded before committing capital.
{ "type": "object", "required": [ "subject" ], "properties": { "subject": { "type": "string", "description": "Ticker symbol or topic phrase to score. Examples: NVDA, \"Bitcoin ETF flows\", \"Tesla robotaxi launch\"." } }, "additionalProperties": false }arguments 13 linesdisinfo-alert reads unknown never probed
Monitor a topic or ticker for ongoing disinformation patterns and coordinated narratives. Scores recent signals against detection rules, filters by a severity threshold, and returns the detected patterns, source diversity, and a summary so a workflow can act on the verdict.
{ "type": "object", "required": [ "subject", "severity_threshold" ], "properties": { "subject": { "type": "string", "description": "Ticker symbol, topic phrase, or named narrative to monitor. Examples: TSLA, \"AI bubble\", \"election fraud claims\"." }, "severity_threshold": { "enum": [ "low", "medium", "high" ], "type": "string", "description": "Minimum pattern strength to include. Required: one of low, medium, or high." } }, "additionalProperties": false }arguments 23 linesnotification-prefs changes data unknown never probed
Read or change which Verity emails you receive: the daily brief, the market pulse, anomaly alerts, the weekly digest, and product news. Turn any category off, or turn one back on. Account and billing messages are always sent and are not controlled here.
{ "type": "object", "required": [ "action" ], "properties": { "prefs": { "type": "object", "properties": { "alerts": { "type": "boolean", "description": "Alerts when Verity flags coordinated activity on a ticker you follow." }, "market_pulse": { "type": "boolean", "description": "The daily market-wide read." }, "morning_brief": { "type": "boolean", "description": "Your daily watchlist brief and the Sunday week-ahead outlook." }, "weekly_digest": { "type": "boolean", "description": "Periodic summaries such as the monthly wrap-up." }, "product_marketing": { "type": "boolean", "description": "Occasional product and feature updates." } }, "description": "Only for 'set'. List each category you want to change, mapped to true to receive it or false to stop it.", "additionalProperties": false }, "action": { "enum": [ "get", "set" ], "type": "string", "description": "Use 'get' to read your current preferences, or 'set' to change them." } }, "additionalProperties": false }arguments 44 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idaa69e2c3c05486eb.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/aa69e2c3c05486eb/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/aa69e2c3c05486eb?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.