Should my agent depend on the MCP server io.github.maco144/nullcone?

Verdict: allow — mid-solo — safe to depend on As of 2026-09-06T06:21:45Z: a dated observation with receipts, not a warranty.

Nullcone Threat Intelligence

io.github.maco144/nullcone

Real-time threat intel for AI agents: 890K+ IOCs incl. prompt-injection & AI-skill threats

— the operator's own registry description reported

Publisher io.github.maco144 · first seen 2026-08-12 · endpoint https://nullcone.ai/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · action ● · V n/a

allow — because answers ●, 30 tools legible (band A) ●, no confirmed drift in 6 probes ●; not yet checked: truth (0 runs)

Cluster mid-solo · distinctiveness 0.641 (unusual). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency94 ms

vs populationtypical

protocolcurrent

authopen

Can it be used? Q4 · observed

tools30

vs populationhigh

capabilities4

harnessA

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_a054b199fd8018d54fa3df37 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Q1Does it answer?alive & usable — 6 probes ●evidence ↓

Q2What is it?action ● evidence ↓

Q3Can it be checked?V n/a for this kind ◐evidence ↓

Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?mid-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (6 shown, 2026-08-12 → 2026-09-06). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (2 events)

date	type	what changed
2026-08-23	outcome	ok_tools (was timeout)
2026-08-12	outcome	first probe: timeout

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

nature	tools	meaning	what checking applies
action	11	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public	9	serves public facts	truth-checkable against a public source — the V-ladder applies in full
computational	7	deterministic transforms	self-checkable by re-computation and known-answer tests
unclassified	3	not classifiable from its text	Tier-1 only until its tools describe themselves

Tools last seen observed

check_freshness check_prompt check_prompt_batch drain_subscription family_threats fingerprint_tool_metadata freshness_limits get_new_threats get_stats is_ioc_revoked list_families list_revocations list_subscriptions lookup_ioc poll_since prompt_cache_stats recent_threats registry_flagged_tools registry_monitor_stats report_detection revoke_ioc scan_skill_content search_by_type submit_batch submit_ioc subscribe_threats unsubscribe validate_skill vote_false_positive warm_prompt_cache

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	30/30	✓
has a description	30/30	✓
description is substantive	30/30	✓
parameters are typed	30/30	✓
parameters are described	8/30	8/30

30 of 30 tools graded · 30 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

1.29.0

server version Nullcone Threat Intelligence

Capabilities: experimental prompts resources tools

Drift observed

No confirmed drift on record. Baseline set 2026-09-06; changes appear here after human review.

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-06T06:16:20Z	ok_tools	200	94	2025-06-18
2026-08-30T06:15:53Z	ok_tools	200	100	2025-06-18
2026-08-23T06:13:33Z	ok_tools	200	109	2025-06-18
2026-08-16T06:13:18Z	timeout		12057
2026-08-14T19:59:45Z	timeout		12102
2026-08-12T05:34:58Z	timeout		12059

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/io.github.maco144/nullcone.svg)](https://robinsaige.com/s/io.github.maco144/nullcone)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →