Verity Skills

io.github.cchurctripPublished by GitHub account cchurctripv1.0.1Updated Nov 2, 2026

Real-time social media and prediction market integrity layer for traders, funds, and quant desks.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server giving an AI assistant pre-trade integrity checks on social media and prediction market activity for tickers, topics and claims.

What you can do
  • Score a topic, ticker or narrative for coordinated activity and get a composite integrity score for a market subject
  • Run a real-time scan of a topic, ticker or claim and cross-reference claims against monitored sources
  • Monitor a topic or ticker for disinformation patterns
  • Produce a daily briefing of overnight signals across a watchlist
When to use it
Useful for traders, funds and quant desks that want an assistant to run a quick integrity check on a ticker, narrative or claim before acting on it, or to keep a watchlist monitored for coordinated activity and disinformation.
Requirements
A remote HTTP endpoint; no local package. A Verity API key is required for every skill, sent as an Authorization bearer token. A seven-day trial is offered without a credit card.
Before you install
Every skill requires the Authorization bearer token, so the key is shared with the Verity service. Trial usage is capped and returns an upgrade prompt when the cap is reached. Signals and scores are third-party assessments, not verified facts, and should not be treated as trading advice.

Installation

In SourceWeft

  1. Open Verity Skills in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.cchurctrip%2Fverity/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "verity-skills": {
      "type": "http",
      "url": "https://mcp.verityskills.com/mcp"
    }
  }
}

README

Verity MCP Server

Public MCP (Model Context Protocol) server for Verity skills. Six callable endpoints your AI agent can invoke before any trade: detect coordinated activity, score market subjects, cross-check claims, flag disinformation patterns.

Production endpoint: https://mcp.verityskills.com/mcp

Why Verity skills

ApeWisdom has a dashboard. StockTwits has a feed. Verity has skills. The pre-trade integrity check most AI workflows are missing. Connect once; every Verity capability becomes a function call from inside your Claude, Cursor, LangChain, or LlamaIndex workflow.

Every skill needs a Verity API key. Issue one in seconds at https://verityskills.com/account/api-keys.

Install

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows). Native HTTP transport (Claude Desktop 2026 builds):

json
{  "mcpServers": {    "verity": {      "type": "http",      "url": "https://mcp.verityskills.com/mcp",      "headers": {        "Authorization": "Bearer vtk_<your-token>"      }    }  }}

If your Claude Desktop is older and rejects type: "http", use the mcp-remote stdio bridge. See docs/CLAUDE_DESKTOP.md for the full guide. Fully quit Claude Desktop (Cmd-Q on macOS) before relaunch.

Cursor

Add to ~/.cursor/mcp.json:

json
{  "mcpServers": {    "verity": {      "url": "https://mcp.verityskills.com/mcp",      "headers": {        "Authorization": "Bearer vtk_<your-token>"      }    }  }}

Restart Cursor. See docs/CURSOR.md for the full guide.

Direct API (curl, no MCP client required)

bash
curl -sS -X POST https://mcp.verityskills.com/mcp \  -H 'content-type: application/json' \  -H 'Authorization: Bearer vtk_your_key_here' \  -d '{    "jsonrpc": "2.0",    "id": 1,    "method": "tools/call",    "params": {      "name": "coordination-heat",      "arguments": { "subject": "GME" }    }  }'

All six skills require an API key issued at https://verityskills.com/account/api-keys.

Other agent runtimes

Any MCP-compliant agent runtime works. The endpoint is https://mcp.verityskills.com/mcp over HTTP+SSE (the SSE channel is a future addition; HTTP POST works today). Add Authorization: Bearer vtk_<token> for every skill.

Available skills

SkillAuthCapability
coordination-heatRequiredScore a topic, ticker, or narrative for coordinated activity.
verity-scoreRequiredComposite integrity score for a market subject.
morning-briefRequiredDaily briefing of overnight signals across a watchlist.
verity-scanRequiredReal-time scan of a topic, ticker, or claim.
cross-check-alertRequiredCross-reference a claim against monitored sources.
disinfo-alertRequiredMonitor a topic or ticker for disinformation patterns.

Marketplace listings

Architecture

Thin bearer-token proxy on Cloudflare Workers. Zero state, zero DB credentials.

  • Translates Authorization: Bearer vtk_* from MCP clients into the upstream x-verity-key header for verityskills.com skill routes.
  • JSON-RPC 2.0 framing per the MCP spec (2025-03-26).
  • 402 TRIAL_CAP_REACHED responses are rewritten to inject an absolute upgrade_url so MCP clients can route trial-cap users to the right upgrade page.
  • 5xx upstream responses are wrapped as JSON-RPC -32603 envelopes with HTTP 200 to keep transport-layer retry semantics correct.
  • Per-tool kill switch via the MCP_TOOLS_DISABLED Wrangler secret. Global kill switch via MCP_KILL_SWITCH=on.
  • Sentry instrumentation via @sentry/cloudflare. Bearer tokens are scrubbed from any captured event via a beforeSend hook.

Operations

ConcernSource
Deploy + secrets + DNSdocs/DEPLOY_RUNBOOK.md
Post-deploy smokescripts/post-deploy-smoke.sh <base-url>
Synthetic monitoring5-minute cron at cchurctrip/verity:app/api/cron/mcp-synthetic-smoke/route.ts
Health endpointGET https://mcp.verityskills.com/health
Marketplace submissiondocs/SMITHERY.md, docs/CURSOR.md

Development

bash
git clone https://github.com/cchurctrip/verity-mcpcd verity-mcpnpm installnpm test            # 237 unit + property + integration testsnpm run lintnpm run typechecknpm run check-manifestnpx wrangler dev    # local worker on http://localhost:8787

License

MIT. See LICENSE.

Source: README.md at commit b70ddca

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts