MCP servers › net.congressio › congressio
MCP server · registry snapshot 2026-11-08 · last tested 2026-11-21
congressio MCP server
Registry name net.congressio/congressio
by congressio.net · domain (the registry's namespace rule)source link does not open (missing or private)npm ↗Website ↗
Manage an academic conference: papers, peer review, decisions and attendees. — the publisher's description
Summary
net.congressio/congressio is a remote and local MCP server listed in the official MCP registry at version 0.1.1, under the namespace of the domain congressio.net. Its linked repository, github.com/greg-rivtech/confhub, does not open publicly (missing or private). On 2026-11-21 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 21 tools, 0 resources and 0 prompts.
Record checks
4 of 6 record checks met · 3 do not apply
- met: Registry entry is active and says how to run it
- not met: Source repository link opens
- not applicable: Repository is not archived
- not applicable: Code pushed to the repository in the 90 days before our check
- not applicable: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #8,320 of 20,725 packages by monthly downloads, tied with 22 others
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- no known high or critical advisories
- Repository
- link does not open publicly
- Tools
- 21
- Last tested
- 2026-11-21
Tool list at the three APIs
Not sent yet for this version (0.1.1).
Worth knowing before you connect it
- The linked repository does not open publicly, so the code cannot be reviewed through it.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-21
- Mode
- read-only (no tool calls)
- Latest version
- 0.1.1, published 2026-11-07 (registry, as of the 2026-11-08 snapshot)
- First listed version
- 2026-11-07 (earliest version still in the registry; older removed versions would be earlier)
- Registry data
- snapshot 2026-11-08
- Package and repository
- checked 2026-11-08
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
1 found in the records we hold
- The repository link does not open: GitHub answered HTTP 404 (it does not exist, or it is private). — api.github.com · 2026-11-08 · all servers with this fact
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn. Does not apply: repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
New in the registry: not in the list of 2026-11-07, listed on 2026-11-08 with version 0.1.1 (published 2026-11-07).
Source: the official MCP Registry list on 2026-11-07 and on 2026-11-08.
What it is
What does this server offer?
Observed inventoryNone of its 21 tools are described as changing anything. For 21 the reading was uncertain, so no mark is shown.
- list_public_conferences
“List the conferences published on Congressio — name, slug, dates, timezone, venue, organizer, and whether the program is published.”
Publisher declares: read-only yes · open-world yes
2 inputs
limitinteger“How many to return (default 50, max 100).”offsetinteger“How many to skip, for paging.”
- get_public_conference
“Fetch one publicly visible conference by its URL slug — dates, timezone, venue, organizer, program status, and the link to its public page.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
slugstringrequired“The conference's URL slug, as it appears in /events/<slug> and in list_public_conferences.”
- list_my_eventson 3 other servers
“List every event belonging to the API key's organization, including drafts and archived ones, with their UUIDs.”
Publisher declares: read-only yes · open-world yes
2 inputs
limitintegeroffsetinteger
- list_submissionson 18 other servers
“List the papers and abstracts submitted to one of the organization's events, with each submission's review status and track.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”limitintegeroffsetinteger
- get_submissionon 11 other servers
“Read a single paper in full: its title, track, status, the reviews written on it with each reviewer's scores and comments, the average per criterion, any rebuttal from the authors, the meta-review, a…”
Publisher declares: read-only yes · open-world yes
2 inputs, 2 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”submissionIdstringrequired“Submission UUID from list_submissions.”
- list_reviewerson 2 other servers
“List everyone who reviews for one of the organization's conferences, with the tracks each covers, their free-text expertise, and how many reviews they are already carrying.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”
- list_trackson 11 other servers
“List the tracks (also called topics or categories) a conference accepts submissions under, with how many papers are in each.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”
- list_formson 62 other servers
“List the forms attached to one of the organization's conferences — the call for papers, the registration form, and any decision forms — with how many questions each has and whether it is published.”
Publisher declares: read-only yes · open-world yes
1 input, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”
- create_call_for_papers
“Create the submission form authors fill in — the questions a call for papers asks, such as a title, an abstract, a track and a file upload.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
3 inputs, 3 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”namestringrequired“What the form is called, e.g.”questionsarrayrequired“The questions, in the order authors will see them.”
- list_registrationson 7 other servers
“List the confirmed attendees of one of the organization's events — name, email, ticket tier, and whether the registration is paid.”
Publisher declares: read-only yes · open-world yes
3 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”limitintegeroffsetinteger
- register_attendee
“Register one attendee for an event and issue their QR pass — the programmatic equivalent of a walk-up registration, useful for importing someone from another system.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
4 inputs, 3 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”namestringrequired“The attendee's full name, as it should appear on the badge.”emailstringrequired“The attendee's email.”tierstring“Ticket tier — the value or label of an option on the event's registration form.”
- create_draft_conference
“Create a new conference as a DRAFT — it is not publicly visible until someone publishes it in Congressio, so this is safe to use while still deciding details.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
5 inputs, 2 required
namestringrequired“The conference name, as attendees will see it.”timezonestringrequired“IANA timezone, e.g.”descriptionstringstartDatestring“ISO date (YYYY-MM-DD).”endDatestring“ISO date (YYYY-MM-DD).”
Show 9 more tools
- update_conference
“Change a conference's name, dates, venue or URL slug.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
11 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”namestringslugstring“Lowercase letters, numbers and hyphens.”descriptionstringstartDatestring“ISO date (YYYY-MM-DD), in the conference's timezone.”endDatestring“ISO date (YYYY-MM-DD).”venueNamestringvenueAddressstringvenueCitystringvenuePostalCodestringvenueCountrystring
- set_conference_windows
“Set when the call for papers and registration open and close.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
5 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”submissionOpenstring or null“ISO 8601 date-time when the CFP opens, or null to remove the bound.”submissionClosestring or null“ISO 8601 submission deadline, or null to remove it (CFP stays open).”registrationOpenstring or nullregistrationClosestring or null
- publish_conference
“Publish a DRAFT conference so it becomes publicly visible: it appears in the directory, its pages resolve, and its call for papers opens to authors.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
2 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”acknowledgeMissingarray“ONLY the setup item keys a previous call reported as missing, copied verbatim after the user agreed to publish anyway.”
- add_reviewer
“Give someone the reviewer role for a conference, by email address.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”emailstringrequired“The reviewer's email address.”categoryIdsarray“Track or category ids to scope this reviewer to.”
- assign_reviewer
“Assign one of the conference's reviewers to review one submission.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
3 inputs, 3 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”submissionIdstringrequired“Submission UUID from list_submissions.”reviewerIdstringrequired“The reviewer's user id.”
- record_decisionon 19 other servers
“Record an accept, reject or revise outcome on a single paper, optionally with private notes and feedback for the author.”
Publisher declares: read-only no · destructive no · idempotent yes · open-world yes
5 inputs, 3 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”submissionIdstringrequired“Submission UUID from list_submissions or get_submission.”decisionstringrequired“The decision type's name as configured on this event, e.g.”notesstring“Private notes for the organizers.”authorFeedbackstring“Feedback the author WILL see — but only once decisions are released, not now.”
- release_decisions
“⚠️ THE MOST CONSEQUENTIAL TOOL HERE.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
2 inputs, 1 required
eventIdstringrequired“Event UUID from list_my_events — not the URL slug.”confirmAuthorsToEmailinteger“ONLY after step 1 reported this exact count AND the user explicitly agreed to send.”
- send_feedbackon 104 other servers
“Send the user's feedback about Congressio's AI connector to the Congressio team — what worked, what was confusing, what a tool got wrong.”
Publisher declares: read-only no · destructive no · idempotent no · open-world yes
4 inputs, 1 required
messagestringrequired“The user's feedback, in their own words.”toolNamestring“Which tool the problem was about, if there was one — e.g.”transcriptstring“The conversation, ONLY if the user explicitly agreed to share it.”transcriptConsentboolean“True only when the user has been asked, in the terms described above, and clearly said yes.”
- read_documentationon 4 other servers
“Read Congressio's own documentation as Markdown.”
Publisher declares: read-only yes · open-world yes
1 input
slugstring“A documentation page slug.”
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-21; remote servers are read the day they appear and again about every 30 days; package servers at the monthly refresh.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 75% of 64
- Tools with a description
- 100% of 21
- Typical description length
- 785 characters
The tool set
Counted from the listing
- Tools
- 21
- Size of the list
- about 8,493 tokens for an agent to load (characters ÷ 4)
- Naming
- 21 of 21 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 21 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package @congressio/mcp
Our sandbox started this package on 2026-11-21 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"congressio": {
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"congressio": {
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"congressio": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"congressio","type":"stdio","command":"npx","args":["-y","@congressio/mcp@0.1.1"]}'Claude Code
claude mcp add --transport stdio congressio -- npx -y @congressio/mcp@0.1.1
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"congressio": {
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"congressio": {
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.congressio] command = "npx" args = ["-y", "@congressio/mcp@0.1.1"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"congressio": {
"command": "npx",
"args": [
"-y",
"@congressio/mcp@0.1.1"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @congressio/mcp@0.1.1
- Optional settings the entry also lists (left out above): CONGRESSIO_API_KEY, CONGRESSIO_BASE_URL.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://www.congressio.net/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"congressio": {
"url": "https://www.congressio.net/api/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"congressio": {
"type": "http",
"url": "https://www.congressio.net/api/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"congressio","type":"http","url":"https://www.congressio.net/api/mcp"}'Claude Code
claude mcp add --transport http congressio https://www.congressio.net/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"congressio": {
"type": "streamableHttp",
"url": "https://www.congressio.net/api/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"congressio": {
"httpUrl": "https://www.congressio.net/api/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.congressio] url = "https://www.congressio.net/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"congressio": {
"url": "https://www.congressio.net/api/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://www.congressio.net/api/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.1.1
- Latest stable
- 0.1.1
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-08; new versions read the day they appear; the rest re-read about every 30 days. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-08 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-ZyXXVHX6RyYDpU9Bd…
- Signature
- signed
- License
- MIT
Source: the package registry · 2026-11-08.
Usage
- Downloads
- 510 in the last month
Source: api.npmjs.org · 2026-11-08.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.1.1). Source: read 2026-11-10.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: read 2026-11-10.
- Node.js version (npm). Needs Node 20 or later (engines.node
>=20). Source: read 2026-11-10. - MCP SDK in the package files. Ships no MCP SDK code in its own files by our rule, and does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency. Source: read 2026-11-10. - Build workflow. No build provenance published for this version. Source: read 2026-11-10.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-10.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-12. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-12. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-12. Source: read 2026-11-12.
- Cline marketplace. Not in the Cline marketplace on 2026-11-12. Source: read 2026-11-12.
Own host
- security.txt. No security.txt at https://www.congressio.net/.well-known/ (HTTP 404, 2026-11-10). Source: www.congressio.net/.well-known/security.txt · read 2026-11-10.
- A2A agent card. No A2A agent card at https://www.congressio.net/.well-known/ (HTTP 404, 2026-11-10). Source: www.congressio.net/.well-known/agent-card.json · read 2026-11-10.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint www.congressio.net/api/mcp | Endpoint answered and asked for sign-in | matches | our test · 2026-11-08 |
| No credential declared as required | Required sign-in | differs | our test · 2026-11-08 |
| Published package can be started | Started and answered | matches | our test · 2026-11-21 |
| Version 0.1.1 on npm | Exists and can be installed | matches | npm · 2026-11-08 |
| Repository github.com/greg-rivtech/confhub | Does not open (not found or private) | differs | api.github.com · 2026-11-08 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- net.congressio
- Repository
- github.com/greg-rivtech/confhub — does not open publicly
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-11-08; security policy read from GitHub · 2026-11-08; read when the server is listed, then about every 30 days; an operator can ask for an earlier re-read.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating4 of 6 record checks met · 3 do not apply
- #8,320 of 20,725 packages by monthly downloads, tied with 22 others
- Not ranked by stars: no public GitHub repository
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- Does not applyRepository is not archivedNo public GitHub repository to read.
- Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
- Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-08 (security policy 2026-11-08). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about net.congressio/congressio
Answered from the data aboveWho publishes net.congressio/congressio?
The registry ties the namespace net.congressio to the domain congressio.net; only its owner can publish under it. Its linked repository, github.com/greg-rivtech/confhub, does not open publicly (missing or private). These are facts from the registry and GitHub, not a rating.
Is net.congressio/congressio safe to install?
We do not rate servers as safe or unsafe. 4 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has net.congressio/congressio been security tested?
Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. ProtocolProbe publishes no security verdict for a named server.
Does net.congressio/congressio publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.1.1, the latest stable release on npm.
Where is the source code of net.congressio/congressio?
The registry links to github.com/greg-rivtech/confhub, but that link does not open publicly, so the code cannot be inspected through it.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-11-21, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model. This server also has a remote test (0 of 17 applicable checks exercised).
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted the published package in an isolated sandbox (read-only mode)
- 1,843 msConnected after 0 redirects.
- Read the inventory: 21 tools, 0 resources, 0 prompts.
- 3,418 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why. How often each is read again: methodology.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “net.congressio/congressio: MCP server record.” Data checked 2026-11-21. https://protocolprobe.com/mcp/servers/net.congressio/congressio
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/net.congressio/congressio)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology