Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Oravan

REMOTE · ORAVAN.ORG

Nonpartisan U.S. Congress data: bill decodes, rep lookup, bilingual EN/ES, read-only, no accounts.

Available components

0 this week 86 Trust /100

Last scanned (18 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 7 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1023 tokens (~204/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 8 Aug 26 0
    • Tool “get_bill” rewrote its description, which is the text the model reads security
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 7 Nov 2026 · Probed https://oravan.org/api/mcp/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=oravan.org CN=YR1,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 RSA 2048 SHA256-RSA 5c139faf9de1746537e1d22b233ee8b64b1
SANs: oravan.org
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of oravan.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725, 26974 8, 8 Verified
oravan.org. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000
content-security-policy frame-ancestors 'self'
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://oravan.org/api/mcp/mcp Verified 200
http (plaintext) http://oravan.org/api/mcp/mcp HTTPS enforced 308 https://oravan.org/api/mcp/mcp
MCP tools · 5 exposed · ~1,023 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_bill ~307

Get the full plain-language decode of a federal bill by slug (e.g. "hr-2701-119") or citation (e.g. "H.R. 2701" - resolves to the most recent Congress on a match). Returns the AI-generated summary (headline, tl;dr, what/who/why/cost - automatically checked before publish and clearly labeled when present), the official status in plain language, a decision_state (pending, settled or enacted, with the official record's own sentence in settled_reason once the decision is settled or enacted), an urgency band and an urgency_score (the score is ranked from status and recency alone; decision_state, not the score, says whether a decision is still ahead), sponsor, key dates, the official Congress.gov page, and - while the decision is still pending - an act_url to Oravan's on-site call flow. This tool never drafts a phone script - script generation happens only on-site, where the caller reads and can edit the script before dialing; that is not available over this API.

NameTypeReqDescription
citationstring–Bill citation, e.g. "H.R. 2701" or "S.J.Res. 99". Used only when slug is omitted.
localestring–Response language: "en" (default) or "es".
slugstring–Bill slug, e.g. "hr-2701-119". Takes priority over citation when both are given.

No output schema declared.

No examples provided.

get_representative ~95

Get full details for one member of Congress by bioguide ID (e.g. "W000797"), plus their 5 most recently active sponsored bills. Facts only: no scorecards, ratings, or vote grades.

NameTypeReqDescription
bioguidestringyesBioguide ID, e.g. "W000797".
localestring–Response language: "en" (default) or "es".

No output schema declared.

No examples provided.

lookup_representatives ~208

Look up a person's U.S. House member and two Senators by 5-digit ZIP code. Returns each member's name, party, phone, official website, portrait URL, and district office phone numbers - the number a constituent should actually call. Some ZIP codes span more than one congressional district (needs_address: true, all candidate districts returned); this tool does not perform address-level refinement itself in this release - point the person to the response's reps_url, where a stateless, unlogged Census-geocoder proxy narrows it to a single district from a street address that Oravan never stores. When a House seat currently has no member, `vacancies` lists the empty seat(s) (state + district) explicitly - the departed member is never returned as if still serving, and no election timeline is implied.

NameTypeReqDescription
localestring–Response language: "en" (default) or "es".
zipstringyes5-digit U.S. ZIP code.

No output schema declared.

No examples provided.

search_bills ~232

Search Oravan's bilingual federal bill corpus by free-text query, issue topic, status, or active-only. Returns short teasers (headline, status, decision_state, urgency) for matching bills, most urgent first. The urgency_score is ranked from status and recency alone; decision_state says whether a decision is still ahead.

NameTypeReqDescription
active_onlyboolean–Exclude signed/vetoed (terminal) bills when true.
limitinteger–Max results (default 20, max 50).
localestring–Response language: "en" (default) or "es".
querystring–Free-text search. Every word must appear somewhere in the bill title, short title, plain-language headline and summary, or topic names (any order, accents ignored). A bill number in any common form (…
statusstring–Bill status to filter to.
topicstring–One of the 12 issue categories.

No output schema declared.

No examples provided.

whats_moving ~181

What's moving in Congress recently: active, plain-language-decoded bills that cleared Oravan's 'act now' urgency bar within the last N days (default 7), optionally filtered by topic. Returns an honest empty list with quiet_week: true when nothing has cleared the bar - this tool never pads the list to look busier than Congress actually is this week. If the list is empty because Oravan's own data sync looks stale rather than Congress being quiet, data_stale is set instead so that distinction is never lost.

NameTypeReqDescription
daysinteger–Lookback window in days (default 7).
limitinteger–Max results (default 10, max 50).
localestring–Response language: "en" (default) or "es".
topicstring–One of the 12 issue categories.

No output schema declared.

No examples provided.

Install

How do I install the Oravan MCP server?

Oravan is a hosted endpoint at https://oravan.org/api/mcp/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · oravan.org

# add to Claude Code
claude mcp add --transport http org-oravan-mcp 'https://oravan.org/api/mcp/mcp'
Common questions

What is the Oravan MCP server?

Oravan is an MCP server listed in the public MCP registry as org.oravan/mcp. Nonpartisan U.S. Congress data: bill decodes, rep lookup, bilingual EN/ES, read-only, no accounts. This page covers its hosted endpoint (https://oravan.org/api/mcp/mcp).

Is the Oravan MCP server safe to use?

Oravan scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Oravan MCP server expose?

Oravan exposes 5 tools: lookup_representatives, get_bill, search_bills, whats_moving, get_representative. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.

Does the Oravan MCP server require authentication?

No. We connected to Oravan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Oravan MCP server still maintained?

Oravan is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Oravan MCP server?

VerifyMCP ran 13 checks on Oravan, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.