mcp-registry/io.github.jnilrac/secant-agent-research-mcp · v2.14.7
As of 2026-10-25 21:12 UTC, the Jnilrac Secant Agent Research MCP server is up with a Glimind reliability score of 63/100 (grade C). Over the last 30 days it answered 97.6% of Glimind's liveness checks. It had 635 outages in 90 days, with a median recovery of 5 minutes.
Paid MCP web research for agents: search, extraction, citations, and x402 payment discovery.
Claude Code
claude mcp add --transport http jnilrac-secant-agent-research-mcp-server https://agentic.secantoutreach.com/mcp/
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"jnilrac-secant-agent-research-mcp-server": {
"type": "http",
"url": "https://agentic.secantoutreach.com/mcp/"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
6 of 6 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 →
5 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 →
Reachable 97.6% of the time over the last 30 days; median recovery 5 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.
Handshake + tools/list takes ~2,309 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
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.jnilrac%2Fsecant-agent-research-mcp/fixes
{
"name": "search",
"description": "Paid x402 web search for autonomous agents.",
"inputSchema": {
"type": "object",
"required": [
"query",
"payment"
],
"properties": {
"query": {
"type": "string",
"description": "Search query to run through the paid research API."
},
"payment": {
"type": "object",
"description": "x402 payment proof payload containing resource, amount, wallet, and settlement metadata.",
"additionalProperties": true
},
"max_results": {
"type": "integer",
"default": 10,
"maximum": 10,
"minimum": 1,
"description": "Maximum number of ranked search results to return."
},
"facilitator_id": {
"type": "string",
"default": "evm-base",
"description": "Settlement facilitator id. Use evm-base for Base USDC payments."
},
"payment_identifier": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Optional idempotency key. Reuse it on retries to return the cached paid result."
}
}
},
"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.jnilrac/secant-agent-research-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.jnilrac/secant-agent-research-mcp"}) over MCP.
research_pack ~289 tokensmonitor_diff ~287 tokenssearch ~240 tokenscodex_audit ~223 tokensextract_page ~220 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.jnilrac%2Fsecant-agent-research-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.jnilrac%2Fsecant-agent-research-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jnilrac%2Fsecant-agent-research-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.jnilrac%2Fsecant-agent-research-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.jnilrac%2Fsecant-agent-research-mcp?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:029c61053c643486…, first seen 2026-10-17, included at leaf 16399 of 68,596. Version history · verify what your client received.
Compare: most reliable code servers · most reliable web servers · most reliable other servers · most reliable procurement servers · most reliable research 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-25 21:12 UTC, the Jnilrac Secant Agent Research MCP server is up with a Glimind reliability score of 63/100 (grade C). Over the last 30 days it answered 97.6% of Glimind's liveness checks. It had 635 outages in 90 days, with a median recovery of 5 minutes.
Jnilrac Secant Agent Research MCP server advertises 6 tools, including codex_audit, extract_page, monitor_diff, procure_request, research_pack.
Point your MCP client at this streamable-http endpoint: https://agentic.secantoutreach.com/mcp/
Glimind scanned all 6 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.