mcp-registry/io.github.opencallportal/open-call-portals · v1.0.0
As of 2026-10-23 10:41 UTC, the Opencallportal Open Call Portals MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 48 outages in 90 days, with a median recovery of 6 minutes.
Search PII-free opportunities, availability, and live events; prepare safe no-write form handoffs.
Claude Code
claude mcp add --transport http opencallportal-open-call-portals-mcp-ser https://opencallportal.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"opencallportal-open-call-portals-mcp-ser": {
"type": "http",
"url": "https://opencallportal.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
1 tool(s) have no inputSchema or a root that is not {"type":"object"}.
Every tool needs an inputSchema whose root is {"type":"object","properties":{...}} — use {"type":"object","properties":{}} for tools without arguments. Clients reject or mis-call tools without it. How to fix →
1 tool definition(s) exceed ~1,200 tokens each (largest: prepare_listing_form, ~22,369).
Move long reference material out of descriptions (link a doc or expose a resource), drop repeated examples, and collapse large enums. Trimming these to ~600 tokens saves ~21,769 tokens every session. How to fix →
7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
2 parameter(s) across 1 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
Loading this server's tool list costs an agent ~24,934 tokens before any work — more than 95% of MCP servers.
Split rarely-used tools into a separate server or a toolset the client can enable, or expose one "search tools" entry point. Many agents load every connected server's tools into every request. How to fix →
Reachable 99.0% of the time over the last 30 days; median recovery 6 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
In the last 30 days: 0 tool(s) removed and 1 schema change(s).
Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals/fixes
{
"name": "get_opportunity",
"description": "Look up one opportunity by its exact public UI reference (for example DJ-3128) before making any claim about it. Returns only an active, non-deleted, non-membership, non-partner public listing and its allowedResponderRoles. State only fields in the live result; missing means not provided. Never invent volume, frequency, or competition.",
"inputSchema": {
"type": "object",
"required": [
"reference"
],
"properties": {
"reference": {
"type": "string",
"description": "Exact public UI reference."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "get_platform_schema",
"description": "Returns the Open Call Portals discovery contract: portal IDs, field value options, MCP server details, and read-only search metadata. Call this first for autodiscovery before filtering searches.",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "prepare_listing_form",
"description": "Validate a versioned, allowlisted listing-form prefill and return the canonical create-form URL. It supports every mounted form advertised by get_platform_schema (39 portal forms plus live events); the exact portal-specific fields, posting roles, and value shapes are declared in this tool's schema. This is a no-write handoff: it never creates a draft, sends email, verifies a code, or publishes. Do not include email addresses, verification codes, tokens, session IDs, credentials, contact data, or",
"inputSchema": {
"type": "object",
"properties": {}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.opencallportal/open-call-portals"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.opencallportal/open-call-portals"}) over MCP.
prepare_listing_form ~22,369 tokenssearch_open_calls ~852 tokenssearch_availability ~647 tokenssearch_live_events ~529 tokensprepare_response_form ~302 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.opencallportal%2Fopen-call-portals?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:8b18ad31bd0c85a1…, first seen 2026-10-17, included at leaf 11846 of 51,584. Version history · verify what your client received.
Compare: most reliable retrieval servers · most reliable knowledge servers · most reliable productivity servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 10:41 UTC, the Opencallportal Open Call Portals MCP server is up with a Glimind reliability score of 76/100 (grade B). Over the last 30 days it answered 99% of Glimind's liveness checks. It had 48 outages in 90 days, with a median recovery of 6 minutes.
Opencallportal Open Call Portals MCP server advertises 7 tools, including get_opportunity, get_platform_schema, prepare_listing_form, prepare_response_form, search_availability.
Point your MCP client at this streamable-http endpoint: https://opencallportal.com/mcp
Glimind scanned all 7 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.