MCP servers › ai.nerdnoir › nerdy
MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19
nerdy MCP server
Registry name ai.nerdnoir/nerdy
Nerdy by Nerd/Noir — the publisher's title
by nerdnoir.ai · domain (the registry's namespace rule)Website ↗
A field manual for product and engineering leaders. Search it, or build its nine frameworks. — the publisher's description
Summary
ai.nerdnoir/nerdy is a remote MCP server listed in the official MCP registry at version 4.1.0, under the namespace of the domain nerdnoir.ai. On 2026-11-19 ProtocolProbe connected to it in read-only mode and read its inventory: 23 tools, 255 resources and 92 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
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote (hosted by the publisher)
- Transport
- streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- none needed to open a session
- Tools
- 23
- Last tested
- 2026-11-19
How a client gets in
Connects without signing in
Read from the server's public metadata on 2026-11-19 (nerdnoir.ai), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list at the three APIs
Not sent yet for this version (4.1.0).
Observed fact
This server accepted a session without any credential and lists 10 tools whose name or declaration suggests they change data (tools_create_document, tools_apply_commands, spaces_create_space, spaces_unshare_document, spaces_transfer_document and 5 more). That is our reading of the names; we did not call them. Source: our connection, 2026-11-19.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-11-19
- Mode
- read-only (no tool calls)
- Latest version
- 4.1.0, published 2026-11-18 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-15 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-15 to 2026-11-18; 3 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 3 versions
4.1.0· 2026-11-184.0.0· 2026-11-163.1.0· 2026-11-15
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 4.0.0 (published 2026-11-16) → 4.1.0 (published 2026-11-18), between the registry lists of 2026-11-18 and 2026-11-19.
No release note: the registry entry links no GitHub repository.
Source: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
What does this server offer?
Observed inventoryNone of its 23 tools are described as changing anything. For 23 the reading was uncertain, so no mark is shown.
- search_collectionon 3 other servers
“Semantic search across the collection, the same engine as the chat on nerdnoir.ai.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs, 1 required
querystringrequired“What to look for, in plain words.”limitinteger“Maximum results to return (default 10, max 50).”filtersarray“Frontmatter filters.”
- get_noteon 14 other servers
“Retrieve the full markdown body of a single note by its slug (e.g.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
slugstringrequired“Note slug, e.g.”
- list_by_tagon 2 other servers
“List every published note that carries a tag, with its slug, title, category, and excerpt.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
tagstringrequired“Tag name, case-insensitive.”
- list_by_categoryon 1 other server
“Return all published notes in a given top-level category.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
categorystringrequired“Top-level category slug, e.g.”
- list_backlinkson 2 other servers
“Return the set of notes that wikilink to the given slug.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
slugstringrequired“Target note slug.”
- tools_list_documents
“Return the tool documents the signed-in user owns or shares through a Space, most recently edited first, with each one's id, tool, version, role, Space, and url (the page that opens it in its builder…”
Publisher declares: read-only yes · destructive no · open-world no
1 input
toolKeystring“Which builder: ost | usm | cfd | vsm | noice | wardley | roi | roadmap | framing.”
- tools_get_document
“Return a document: its toolKey, title, version, url (the page that opens it in its builder), the current state as a projection with real ids, and the commands that tool takes, each with its fields.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
documentIdstringrequired“The document id, from tools_list_documents.”
- tools_get_history
“Return the most recent events on a document, newest first, each with its event id and a plain description.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
documentIdstringrequired“The document id, from tools_list_documents.”limitinteger“How many entries (default 20, max 100).”
- tools_export_document
“Export a document as a file.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs, 1 required
documentIdstringrequired“The document id, from tools_list_documents.”formatstring“json (default) or markdown.”
- tools_create_document
“Create a new, empty document for the signed-in user in one of the builders.”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 1 required
toolKeystringrequired“Which builder: ost | usm | cfd | vsm | noice | wardley | roi | roadmap | framing.”titlestring“Defaults to the builder's own default.”idempotencyKeystring“Your id for this create.”spaceIdstring“A shared Space to start the document in.”
- tools_apply_commands
“Change one document in any builder: roadmap (Outcome-Based Roadmap), roi (ROI Calculator), noice (NOICE Prioritization), ost (Opportunity Solution Tree), usm (User Story Map), vsm (Value Stream Map),…”
Publisher declares: read-only no · destructive yes · open-world no
5 inputs, 4 required
toolKeystringrequired“The document's toolKey, from tools_get_document.”documentIdstringrequired“The document id, from tools_list_documents.”expectedVersionintegerrequired“The version you last read from tools_get_document.”batchIdstring“Your id for this batch.”commandsarrayrequired“Commands from the document's catalog in tools_get_document: each one is its type plus that command's fields.”
- spaces_list_spaces
“Return the user's Spaces with each one's id, kind (private, shared, or cohort: the Space of a workshop cohort the user is in), the user's role (owner, editor, or viewer), and how many notes, document…”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
Show 11 more tools
- spaces_get_space
“Return one Space with its notes in order, its documents (each with the url that opens it in its builder), and its members with their roles.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”
- spaces_create_space
“Make a shared Space owned by the user, optionally with its first notes in order.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
namestringrequired“The Space name.”descriptionstring“One sentence on what the Space is for.”slugsarray“Notes to start with, in order.”
- spaces_share_document
“Put a document in a Space so everyone in it can open it.”
Publisher declares: read-only no · destructive no · open-world no
3 inputs, 1 required
documentIdstringrequired“The document id, from tools_list_documents.”spaceIdstring“An existing Space, from spaces_list_spaces.”newSpaceNamestring“Make a Space with this name instead.”
- spaces_unshare_document
“Take a document out of its Space, so it is personal to its owner again.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
documentIdstringrequired“The document id, from tools_list_documents.”
- spaces_transfer_document
“Make another member of the document's Space the owner of the document.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 2 required
documentIdstringrequired“The document id, from tools_list_documents.”newOwnerIdstringrequired“A member userId from spaces_get_space.”
- spaces_invite_members
“Add up to 20 people to a Space with one role: editor (adds and changes things) or viewer (reads).”
Publisher declares: read-only no · destructive no · open-world no
4 inputs, 2 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”emailsarrayrequired“Email addresses.”rolestring“The role every address gets.”documentIdstring“Open this document for an invited person after they sign in.”
- spaces_remove_member
“Remove a member from a Space.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 2 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”userIdstringrequired“A member userId from spaces_get_space.”
- spaces_leave_space
“Take the signed-in user out of a Space.”
Publisher declares: read-only no · destructive yes · open-world no
1 input, 1 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”
- spaces_add_note
“Add a published page to the end of a Space.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 2 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”slugstringrequired“A page slug from search_collection or get_note, for example "concepts/teaming/team-topologies".”
- spaces_remove_note
“Take a page out of a Space's list.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 2 required
spaceIdstringrequired“The Space id, from spaces_list_spaces.”slugstringrequired“A page slug from search_collection or get_note, for example "concepts/teaming/team-topologies".”
- lil_nerdy_ask_question
“Ask Lil Nerdy, Nerd/Noir's own assistant, and get its answer with the collection pages it drew on.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 1 required
questionstringrequired“The question, in the user’s words.”pagestring“A collection slug the question is about, for example "concepts/teaming/conways-law".”document_idstring“One of the user’s builder documents, from tools_list_documents.”historyarray“Earlier turns of this thread with Lil Nerdy, oldest first, at most 10.”
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. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. 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-11-19.
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
No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).
Counted from the listing
- Parameters with a description
- 100% of 47
- Tools with a description
- 100% of 23
- Typical description length
- 285 characters
The tool set
Counted from the listing
- Tools
- 23
- Size of the list
- about 6,080 tokens for an agent to load (characters ÷ 4)
- Naming
- 23 of 23 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 0 of 23 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. 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-11-19 (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://nerdnoir.ai/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"nerdy": {
"url": "https://nerdnoir.ai/api/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"nerdy": {
"type": "http",
"url": "https://nerdnoir.ai/api/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"nerdy","type":"http","url":"https://nerdnoir.ai/api/mcp"}'Claude Code
claude mcp add --transport http nerdy https://nerdnoir.ai/api/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"nerdy": {
"type": "streamableHttp",
"url": "https://nerdnoir.ai/api/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"nerdy": {
"httpUrl": "https://nerdnoir.ai/api/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.nerdy] url = "https://nerdnoir.ai/api/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"nerdy": {
"url": "https://nerdnoir.ai/api/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://nerdnoir.ai/api/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- 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; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). 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.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- MCP SDK in the package files. Not read yet: added with the next daily run.
- Build workflow. Not read yet: added with the next daily run.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://nerdnoir.ai/.well-known/ (HTTP 404, 2026-11-19). Source: nerdnoir.ai/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://nerdnoir.ai/.well-known/ (HTTP 404, 2026-11-19). Source: nerdnoir.ai/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint nerdnoir.ai/api/mcp | Session opened | matches | our test · 2026-11-19 |
| No credential declared as required | Opened a session without any credential | matches | our test · 2026-11-19 |
Tool list changes
Our reads compared · no tool calledHosted endpoint nerdnoir.ai/api/mcp
2 of 2 comparisons between consecutive reads showed a change (3 reads, 2026-11-16 to 2026-11-19; versions 3.1.0 to 4.1.0).
Last change seen between our reads on 2026-11-17 (version 4.0.0) and 2026-11-19 (version 4.1.0).
Changed (3):
tools_apply_commands: description, input schematools_create_document: input schematools_list_documents: input schemaCompared from the tool lists our read-only connection recorded, separately for each hosted endpoint and each package: each tool's name, title, description, input schema and annotations (the order of keys and of tools is ignored). We see a list only when we read it: a change is shown between the two reads where we first saw it, and anything after 2026-11-19 is not known yet. No tool was called. How it is compared
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.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
- 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-11-19. 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, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about ai.nerdnoir/nerdy
Answered from the data aboveWho publishes ai.nerdnoir/nerdy?
The registry ties the namespace ai.nerdnoir to the domain nerdnoir.ai; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.
Does ai.nerdnoir/nerdy need an API key or sign-in?
It opened a session without any credential on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.
Has ai.nerdnoir/nerdy been security tested?
Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.
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.
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
Open without sign-in
It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. 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: exercised
- Fake assistant turns: exercised
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: exercised
5 exercised11 not run (reason given)2 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised - 12Hidden content
audience-hidingChecks resources that hide content from the user.exercised - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.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, except for a server whose operator has claimed it and given permission (that server's page says so); 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, except for a server whose operator has claimed it and given permission (that server's page says so); 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, except for a server whose operator has claimed it and given permission (that server's page says so); 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, except for a server whose operator has claimed it and given permission (that server's page says so); 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, except for a server whose operator has claimed it and given permission (that server's page says so); 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 - 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
- 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
Source: our own test, 2026-11-19, 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,631 msConnected after 0 redirects. No credential was sent or needed.
- Read the inventory: 23 tools, 255 resources, 92 prompts.
- 23,151 msFinished: 5 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. “ai.nerdnoir/nerdy: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/ai.nerdnoir/nerdy
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/ai.nerdnoir/nerdy)
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, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology