MCP servers › net.fmelo › cognita
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
net.fmelo/cognita
Passive OSINT and security recon: DNS, TLS, email posture, IP reputation, CVE/KEV, CT logs. — the publisher's description
Summary
net.fmelo/cognita is a remote MCP server listed in the official MCP registry at version 1.0.34. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 51 tools, 0 resources and 0 prompts.
Record checks
1 of 2 record checks met · 7 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)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: a remote server publishes no download figure
- Not ranked by stars: no public GitHub repository
From public records, not a safety rating. Each check with its reason
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Sign-in
- none needed to open a session
- Tools
- 51
- Described as changing data
- 0 of 51 toolsAI-classified
- Mainly works on
- nothing outside itself: it only answers questionsAI-classified
- Topic
- securityAI-classified
- Last tested
- 2026-10-23
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 1.0.34, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-16 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-16 to 2026-10-17; 3 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.0.34· 2026-10-171.0.32· 2026-10-171.0.0· 2026-10-16
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.34 (published 2026-10-17).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: nothing outside itself: it only answers questions.
None of its 51 tools are described as changing anything. For 11 the reading was uncertain, so no mark is shown.
- asn_prefixesreads or searches
“List the IP prefixes an autonomous system announces (via RIPEstat), with the network holder — the routed footprint of an ASN.”
1 input, 1 required
asnstringrequired“ASN, e.g.”
- cve_triagereads or searches
“Prioritise a host's internet-exposed CVEs: takes the CVEs from host_exposure (Shodan InternetDB) and enriches each with CISA KEV (confirmed exploited in the wild) and FIRST EPSS (exploit probability)…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Generate lookalike variants of a domain (omission, transposition, homoglyph, adjacent-key, hyphenation and TLD-swap typos) and report which ones actually resolve in DNS — the registered lookalikes wo…”
1 input, 1 required
domainstringrequired“Registrable domain, e.g.”
- email_header_analyzercalculates or converts
“Parse pasted raw email headers: the Received: delivery path with per-hop delays, the SPF/DKIM/DMARC verdicts, the originating IP, and spoofing warnings.”
1 input, 1 required
rawHeadersstringrequired“The raw email headers, copied verbatim from the message source.”
“Ask several independent public resolvers (Google, Cloudflare, DNS.SB, NextDNS) the same record over DNS-over-HTTPS and compare their answers.”
2 inputs, 1 required
namestringrequired“Domain, e.g.”typestring“Record type: A (default), AAAA, CNAME, MX, NS, TXT, SOA or CAA.”
- email_posturereads or searches
“Report a domain's modern email-security records beyond SPF/DMARC/DKIM: MTA-STS (DNS record + fetched policy: enforce/testing mode, max_age, MX), TLS-RPT (reporting address) and BIMI (brand logo + VMC…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- ct_org_searchreads or searches
“Find the certificates that name an ORGANISATION in Certificate Transparency (via crt.sh) and the distinct registrable domains on them — a link from a company name to its domain footprint, complementi…”
1 input, 1 required
organizationstringrequired“Organisation name as it appears on certificates, e.g.”
- geo_routereads or searches
“Show the network path from the caller to a target host on a world map: origin (the caller's IP — the user when the agent runs client-side), destination (the target's geolocation), and the great-circl…”
1 input, 1 required
hoststringrequired“Target host name or IP, e.g.”
- tls_posturereads or searches
“Grade a host's transport security A–F in one call, correlating tls_certificate (validity, chain trust, protocol, key/signature), cert_revocation (OCSP/CRL endpoints, must-staple) and hsts_preload_che…”
2 inputs, 1 required
hoststringrequired“Host name or IP, e.g.”portinteger“TLS port (default 443)”
- feodo_c2_checkreads or searches
“Check an IP against abuse.ch's Feodo Tracker botnet command-and-control blocklist (keyless): a hit means the IP is a known C2 server for a malware family (Emotet, Dridex, QakBot, TrickBot, …), with t…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Fetch and analyse a domain's DMARC record (_dmarc TXT): the policy (none/quarantine/reject) and warnings on a weak or missing policy.”
1 input, 1 required
domainstringrequired“Domain to query, e.g.”
- tranco_rankreads or searches
“Report a domain's popularity on the Tranco research list (keyless): its rank in the top ~1M sites, a band (top-1k/10k/100k/1M or 'unranked'), and how many recent daily lists it appears in.”
1 input, 1 required
domainstringrequired“Domain, e.g.”
Show 39 more tools
- rpki_validationreads or searches
“Validate the BGP route-origin of an IP or prefix against RPKI (via RIPEstat): valid / invalid / unknown for the announcing ASN and covering prefix.”
1 input, 1 required
targetstringrequired“IP address, CIDR prefix, or host name — e.g.”
“Look up a CVE in the NVD (NIST National Vulnerability Database): its description, CVSS base score / severity / vector, CWE weakness IDs, publication dates and references.”
1 input, 1 required
cvestringrequired“CVE ID, e.g.”
- spoofabilityreads or searches
“Judge how easily a domain's mail can be forged by correlating SPF and DMARC into one verdict: 'hardened' (DMARC enforcing), 'partial' (DMARC quarantine) or 'spoofable' (no DMARC or p=none — receivers…”
1 input, 1 required
domainstringrequired“Domain to check, e.g.”
- subdomain_takeover_checkreads or searches
“Check a domain's subdomains (enumerated from Certificate Transparency) for dangling-CNAME takeover risk: a CNAME that delegates to a third-party service (GitHub Pages, S3, Heroku, Azure, Netlify, …) …”
1 input, 1 required
domainstringrequired“Domain, e.g.”
“Inspect the leaf certificate a host serves on a live TLS handshake: subject, issuer, subject-alternative names, validity window and days to expiry, key and signature algorithms, serial, thumbprint, t…”
2 inputs, 1 required
hoststringrequired“Host name or IP, e.g.”portinteger“TLS port (default 443)”
“Resolve DNS records for a host name.”
2 inputs, 1 required
namestringrequired“Host name to query, e.g.”typesarray or null“Optional record types to query (A, AAAA, MX, TXT, NS, CNAME, SOA, PTR, CAA).”
- dshield_ip_checkreads or searches
“Look up an IP's reputation in the SANS Internet Storm Center (DShield) data (keyless): how many attack reports it has across how many target sensors over the observed window, the network/AS it belong…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
- host_exposurereads or searches
“Report a host's internet-facing exposure from Shodan's InternetDB (keyless): open ports, detected products (CPEs), known CVEs, hostnames and tags.”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Run a passive web-security scan of a URL (via Astur).”
1 input, 1 required
urlstringrequired“Absolute http(s) URL to scan, e.g.”
- abuse_contactreads or searches
“Find the abuse-reporting e-mail(s) for an IP (or a host's resolved IP) via RIPEstat's abuse-contact-finder — where to report a scanner or attacker surfaced by ip_reputation.”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Check whether a CVE is in CISA's Known Exploited Vulnerabilities (KEV) catalogue — i.e.”
1 input, 1 required
cvestringrequired“CVE ID, e.g.”
“Reverse-resolve an IP address to its PTR host name(s).”
1 input, 1 required
ipstringrequired“IPv4 or IPv6 address, e.g.”
“Check an IP against GreyNoise's Community data: whether it is internet background 'noise' (a mass scanner) and, if so, GreyNoise's classification — 'malicious', 'benign' (an identified research scann…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
- hsts_preload_checkreads or searches
“Check whether a domain is in the browsers' HSTS preload list (via hstspreload.org's keyless status API): the status (preloaded/pending/unknown), whether it was bulk-imported, and the parent domain it…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- disclosure_contactsreads or searches
“Consolidate where and how to report a security issue for a domain: the owner's own published channel (security_txt — RFC 9116 Contact, Policy, PGP key) and the network operator's registered abuse mai…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
“Look up registration data for a domain or IP via RDAP (the modern JSON successor to WHOIS): handle, name, statuses and lifecycle events, plus the raw record.”
1 input, 1 required
querystringrequired“Domain or IP to look up, e.g.”
- tor_exit_checkreads or searches
“Check whether an IP is a current Tor exit node, from the Tor Project's public bulk exit list (keyless).”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Passively read a site's robots.txt and the sitemap it points to.”
1 input, 1 required
domainstringrequired“Domain or URL, e.g.”
- passive_dnsreads or searches
“Historical DNS resolutions for a domain or IP from Mnemonic's keyless Passive DNS: the answers a name resolved to over time (or the names that pointed at an IP), each with a first/last-seen window an…”
1 input, 1 required
querystringrequired“Domain or IP, e.g.”
“Check whether an IP sits inside a netblock on a curated keyless reputation list — Spamhaus DROP/EDROP (networks judged hijacked or bad-actor-controlled) and FireHOL level1 (a conservative aggregate o…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
“Get a CVE's EPSS score (FIRST's Exploit Prediction Scoring System): the probability (0–1) it will be exploited in the next 30 days, and its percentile rank among all CVEs.”
1 input, 1 required
cvestringrequired“CVE ID, e.g.”
- spf_expandreads or searches
“Fully expand a domain's SPF record: follow every include: and redirect= recursively and count the DNS-lookup mechanisms across the WHOLE tree against the RFC 7208 limit of 10 — the real-world failure…”
1 input, 1 required
domainstringrequired“Domain to query, e.g.”
- asn_relationsreads or searches
“Report an autonomous system's BGP relationships via RIPEstat (keyless): its upstreams (transit providers), downstreams (customers) and peers, from observed AS paths — the neighbour ASNs ordered by ho…”
1 input, 1 required
asnstringrequired“ASN, e.g.”
“Fetch and analyse a domain's SPF record: the parsed DNS-lookup count (RFC 7208 limit is 10), the 'all' qualifier, and warnings on a missing or permissive policy.”
1 input, 1 required
domainstringrequired“Domain to query, e.g.”
- wayback_snapshotreads or searches
“Report the first and most recent captures of a domain in the Internet Archive's Wayback Machine (keyless CDX), with a link to each snapshot — a site-age / history signal (how far back it is archived)…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- cert_revocationreads or searches
“Report the revocation posture of the certificate a host serves: the OCSP responder(s) and CRL distribution point(s) a client could use to check revocation, and whether the certificate is must-staple …”
2 inputs, 1 required
hoststringrequired“Host name or IP, e.g.”portinteger“TLS port (default 443)”
- cert_transparencyreads or searches
“Enumerate a domain's subdomains and certificate-issuance history from public Certificate Transparency logs (crt.sh): the names ever certified under it, issuing CAs, and the issuance span.”
2 inputs, 1 required
domainstringrequired“Domain, e.g.”sincestring or null“Optional cutoff date: a year (2026), year-month (2026-01) or full ISO date (2026-01-26).”
- related_domainsreads or searches
“Find other registrable domains that share a TLS certificate (a common SAN) with the given domain, from Certificate Transparency (crt.sh) — a passive link to sibling properties run on the same certifi…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- zone_transfer_check
“Test whether a domain's authoritative name servers allow a DNS zone transfer (AXFR) — a classic misconfiguration that leaks the entire zone (every hostname it holds) to anyone who asks (RFC 5936: AXF…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- urlscan_lookup
“Search urlscan.io's public scan database (keyless) for a domain or IP: recent public scans of the site itself (its own pages, not other sites that merely load something from it) with each page's fina…”
1 input, 1 required
targetstringrequired“Domain to search, e.g.”
- mx_lookupon 3 other servers
“List a domain's mail exchangers (MX), ordered by preference, with each host's resolved IP addresses.”
1 input, 1 required
domainstringrequired“Domain to query, e.g.”
- dkim_lookup
“Fetch a domain's DKIM public-key record for a given selector (<selector>._domainkey.<domain>).”
2 inputs, 2 required
domainstringrequired“Domain to query, e.g.”selectorstringrequired“DKIM selector, e.g.”
- investigateon 3 other servers
“Run a full reconnaissance sweep of a domain or URL and return a correlated report: web-security grade (via Astur), email-authentication posture (SPF/DMARC), nameservers, MX, registrar, subdomains fro…”
2 inputs, 1 required
targetstringrequired“Domain or URL to investigate, e.g.”depthstring“Depth: "standard" (default) for the quick correlation, or "deep" to add RPKI, disclosure contacts, subdomain takeover, IP reputation verdict, TLS posture and C…”
- wayback_urls
“List a domain's historical URLs captured by the Internet Archive Wayback Machine (CDX API, keyless): old endpoints, forgotten paths and files no longer on the live site, across the domain and its sub…”
1 input, 1 required
domainstringrequired“Domain, e.g.”
- blacklist_checkon 3 other servers
“Check whether a mail server is listed on common email DNS blocklists (DNSBLs).”
1 input, 1 required
targetstringrequired“IP address or domain to check, e.g.”
- ip_reputation_aggregate
“Fold every keyless IP-reputation source into one verdict — clean / suspicious / malicious / unknown: ip_blocklist_check (Spamhaus DROP + FireHOL), ip_reputation (GreyNoise), feodo_c2_check (botnet C2…”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
- asn_geoip
“Geolocate an IP address (or a host's resolved IP): ASN, network organisation, and approximate city/country.”
1 input, 1 required
targetstringrequired“IP address or host name, e.g.”
- security_txt
“Fetch a site's vulnerability-disclosure file (RFC 9116) from /.well-known/security.txt (falling back to /security.txt): the declared security Contact(s), Expires date and whether it has lapsed, PGP E…”
1 input, 1 required
domainstringrequired“Domain or URL, e.g.”
- caa_dnssec
“Report a domain's CAA records (which CAs may issue its certificates) and an indicative DNSSEC signal (DNSKEY presence + Authenticated-Data flag — not a full chain validation).”
1 input, 1 required
domainstringrequired“Domain to query, e.g.”
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. 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-10-23.
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
- Says what the tool does
- 100% of 40 tools
- Says what it returns
- 100% of 40 tools
- States limits, defaults or errors
- 3% of 40 tools
- Says when to use it
- 44% of 9 tools
- Items covered per tool
- 2.9 of 4 on average
Counted from the listing
- Parameters with a description
- 100% of 59
- Tools with a description
- 100% of 51
- Typical description length
- 358 characters
The tool set
Counted from the listing
- Tools
- 51
- Size of the list
- about 7,358 tokens for an agent to load (characters ÷ 4)
- Naming
- 48 of 51 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 40 of 51 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, comparing tools within groups of 40. 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 remote endpoint (Streamable HTTP)
We connected to this URL on 2026-10-23 (a read-only session: no tool was called).
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://cognita.fmelo.net/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cognita": {
"url": "https://cognita.fmelo.net/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"cognita": {
"type": "http",
"url": "https://cognita.fmelo.net/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"cognita","type":"http","url":"https://cognita.fmelo.net/mcp"}'Claude Code
claude mcp add --transport http cognita https://cognita.fmelo.net/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://cognita.fmelo.net/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- 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). 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.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint cognita.fmelo.net/mcp | Session opened | matches | our test · 2026-10-23 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-10-23 |
Choosing
Record checks
Public records · not a safety rating1 of 2 record checks met · 7 do not apply
- Not ranked by downloads: a remote server publishes no download figure
- 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 registry entry gives no repository link.
- 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.
- Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
- Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. 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. How each check works · Leaderboards
Common questions about net.fmelo/cognita
Answered from the data aboveDoes net.fmelo/cognita need an API key or sign-in?
It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.
Has net.fmelo/cognita been security tested?
Partly. 2 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.
What can net.fmelo/cognita do?
It lists 51 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.
Can net.fmelo/cognita change or delete data?
None of its 51 tools is described as changing anything (our AI model's reading of the descriptions; nobody checked it by hand). We did not call any tool.
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.
Similar servers
Same topic · AI-read
- io.github.hashgraph-online/hol-guardHOL Guardalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.dengyier/OpenWorkProofalso has tools that calculates or converts, reads or searchescompare with this one
- com.contrastcyber/apiContrastAPIalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.ethanolivertroy/fedramp-docs-mcpalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.quantakrypto/pqc-toolsquantakrypto pqc-toolsalso has tools that calculates or converts, reads or searchescompare with this one
- io.github.crunchtools/trentinaTrentinaalso has tools that calculates or converts, reads or searchescompare with this one
Active servers whose topic is also “security” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
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 (we call no server's tools)
We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. 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 run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
2 exercised12 not run (reason given)4 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.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 - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 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 opened a session without sign-in, so there is no token flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a read-only session with the server's remote endpoint
- 1,553 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 51 tools, 0 resources, 0 prompts.
- 5,109 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.
“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.fmelo/cognita: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/net.fmelo/cognita
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.fmelo/cognita)
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.
Write to hello@protocolprobe.com · corrections log · methodology