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.

io.github.NellInc/saferagenticai-mcp

REMOTE · MCP.SAFERAGENTICAI.ORG · 2 COMPONENTS

Read-only tools over the Safer Agentic AI framework: 239 patterns + 15 heuristics.

0 this week 76 Trust /100

Last scanned (15 hours ago)

Scores higher than 66% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Security

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 Security63
  • 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 enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 914 tokens (~91/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability check failed: schema churn in the 30 days we've observed: 2 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage70
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 9% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 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 (12)

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

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.

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 →

Registry listing versus package

Where what the registry lists and what we observed about the package disagree. This is read from the stored diagnostics and is never an input to the score.

  • Endpoint address

    Registry says
    https://mcp.saferagenticai.org/mcp
    Package shows
    https://mcp.saferagenticai.org/mcp/

    The registry's URL redirects here, so the authorisation and transport results describe this address rather than the one listed. See the evidence →

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.

  • 2 Nov 26 0
    • Server version: 0.4.0 → 0.4.1 functional
  • 16 Oct 26 −2
    • Stability: pass → fail ▼ security
    • Tool “review_stats” was removed ▼ security
    • Tool “list_unreviewed” was removed ▼ security
    • Server version: 0.3.7 → 0.4.0 functional
  • 1 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Tool “search_patterns” rewrote its description, which is the text the model reads security
    • Server version: 1.28.1 → 0.3.7 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
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 5 Nov 2026 · Probed https://mcp.saferagenticai.org/mcp/ · Declared URL https://mcp.saferagenticai.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=saferagenticai.org CN=WE1,O=Google Trust Services,C=US 12 Oct 2026 10 Jan 2027 ECDSA 256 ECDSA-SHA256 142d059f1c186401130d43e4c2963166
SANs: saferagenticai.org, *.saferagenticai.org
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.saferagenticai.org. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
org. DS published 725, 26974 8, 8 Verified
saferagenticai.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

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

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://mcp.saferagenticai.org/mcp Redirected 307 https://mcp.saferagenticai.org/mcp/
streamable-http · followed https://mcp.saferagenticai.org/mcp/ Verified 200
http (plaintext) http://mcp.saferagenticai.org/mcp Inconclusive 307 http://mcp.saferagenticai.org/mcp/
MCP tools · 10 exposed · ~914 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
find_patterns_for_task ~110

Given a natural-language task description (e.g., 'I'm building a tool-using agent that runs shell commands'), return the most relevant patterns grouped by suite. Use this as a starting point for any cross-cutting design question; then follow up with get_requirement on specific pattern_ids. Defaults to verbosity='compact' (cheap triage); pass 'full' to inline snippets and confidence flags.

NameTypeReqDescription
limitinteger––
taskstringyes–
verbositystring––

No output schema declared.

No examples provided.

get_cross_references ~102

Return outgoing adjacencies for a pattern. `explicit_cross_references` are author-asserted (each pattern's `cross_references` YAML field). `inferred_adjacent` (when include_inferred=true) currently returns *same-suite siblings only* — it does not do semantic similarity. Treat inferred entries as 'neighbours worth scanning,' not as endorsed dependencies.

NameTypeReqDescription
idstringyes–
include_inferredboolean––

No output schema declared.

No examples provided.

get_operational_heuristic ~65

Retrieve a single operational heuristic by id (e.g., 'OH::geoffrey-pattern'). Returns the full entry: principle, framework mapping, evidence sources from production deployment, design patterns, anti-patterns, and discovery narrative.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_requirement ~83

Retrieve one subgoal (framework normative content + Pattern layer guidance) by pattern_id (e.g., 'D3::idx2::sandboxing') or display_id (e.g., 'D3.2'). display_id may resolve to multiple subgoals — underlined variants share display_ids.

NameTypeReqDescription
idstringyes–
include_patternboolean––

No output schema declared.

No examples provided.

get_reverse_references ~55

Return patterns that reference the given pattern_id in their cross_references. Complement to get_cross_references (outgoing); this shows incoming. Use to find all consumers of a given pattern.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

list_operational_heuristics ~123

List operational heuristics distilled from production agentic AI deployment (Claude Code, Rewind). These are cross-cutting safety principles discovered through building and operating AI agents, mapped to framework suites. Optional filters: suite_id (heuristics relevant to a specific suite), query (keyword search across titles and principles). Separate from the normative pattern layer — different category of knowledge.

NameTypeReqDescription
querystring–Keyword search across titles, principles, narratives
suite_idstring–Filter by framework suite (e.g., 'D3', 'I2')

No output schema declared.

No examples provided.

list_requirements ~103

List subgoals matching filters (suite_id, suite_type, content_type, min_confidence, missing_pattern_only). Results capped by limit (default 50, max 100).

NameTypeReqDescription
content_typestring––
include_patternboolean––
limitinteger––
min_confidencestring––
missing_pattern_onlyboolean––
suite_idstring––
suite_typestring––

No output schema declared.

No examples provided.

list_suites ~43

List all 16 suites in the SaferAgenticAI framework (9 drivers + 7 inhibitors) with subgoal counts and titles. Call this first to orient.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

resolve_id ~73

Resolve a loose reference (partial id, display_id, slug fragment, or title keyword) to canonical pattern_id(s). Call this when you have a rough reference and need the exact id before calling get_requirement. Always returns candidates — never 'not found'.

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

search_patterns ~157

Field-weighted keyword search across the framework. Terms match at word starts on lowercased text and are IDF-weighted, so rare terms outrank ubiquitous ones; field weights: title 10x, summary 4x, SFR text 3x (all of a subgoal's SFRs scored as one field), description 2x, pattern body 1x. `matched_in` reports the highest-weighted field that matched. No semantic / embedding search — known limitation, see /mcp.html. Use verbosity='compact' to drop snippets and confidence flags (~70% smaller payload) when triaging.

NameTypeReqDescription
limitinteger––
querystringyes–
verbositystring––

No output schema declared.

No examples provided.

Install

How do I install the io.github.NellInc/saferagenticai-mcp server?

io.github.NellInc/saferagenticai-mcp is a hosted endpoint at https://mcp.saferagenticai.org/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 · mcp.saferagenticai.org

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

What is the io.github.NellInc/saferagenticai-mcp server?

io.github.NellInc/saferagenticai-mcp is listed in the public MCP registry as io.github.NellInc/saferagenticai-mcp. Read-only tools over the Safer Agentic AI framework: 239 patterns + 15 heuristics. This page covers its hosted endpoint (https://mcp.saferagenticai.org/mcp).

Is the io.github.NellInc/saferagenticai-mcp server safe to use?

io.github.NellInc/saferagenticai-mcp scores 76 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 io.github.NellInc/saferagenticai-mcp server expose?

io.github.NellInc/saferagenticai-mcp exposes 10 tools: list_suites, get_requirement, list_requirements, search_patterns, get_cross_references, and 5 more. Their descriptions and schemas cost roughly 914 tokens of context every time the server is loaded.

Does the io.github.NellInc/saferagenticai-mcp server require authentication?

No. We connected to io.github.NellInc/saferagenticai-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.NellInc/saferagenticai-mcp server still maintained?

io.github.NellInc/saferagenticai-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.NellInc/saferagenticai-mcp server?

VerifyMCP ran 12 checks on io.github.NellInc/saferagenticai-mcp, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about io.github.NellInc/saferagenticai-mcp: HTTPS. 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.