io.github.kody-w/raptr-names
REMOTE · AIRAPTR-API.AZUREWEBSITES.NET
Name a business or project; check which domains and GitHub names are free, with prices.
Available components
Last scanned (18 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Marketing and SEO
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 425 tokens (~106/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 20. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 13. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Oct 26 67
First indexed and scored.
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 16 Oct 2026 · Probed https://airaptr-api.azurewebsites.net/names/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.azurewebsites.net,O=Microsoft Corporation,L=Redmond,ST=WA,C=US | CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US | 14 Oct 2026 | 21 Jan 2027 | RSA 2048 | SHA384-RSA | 5501362c6060c981556ae8d176000001362c60 |
| SANs: *.azurewebsites.net, *.scm.azurewebsites.net, *.sso.azurewebsites.net, *.eastus2-01.azurewebsites.net, *.scm.eastus2-01.azurewebsites.net, *.sso.eastus2-01.azurewebsites.net, *.eastus2.c.azurewebsites.net, *.scm.eastus2.c.azurewebsites.net, *.sso.eastus2.c.azurewebsites.net, *.02.eastus2.c.azurewebsites.net, *.scm.02.eastus2.c.azurewebsites.net, *.sso.02.eastus2.c.azurewebsites.net and 18 more | ||||||
| CN=Microsoft TLS G2 RSA CA OCSP 16,O=Microsoft Corporation,C=US (CA) | CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US | 1 Aug 2025 | 3 Jun 2029 | RSA 4096 | SHA384-RSA | 330000000e42938f25dc51a99b00000000000e |
| CN=Microsoft TLS RSA Root G2,O=Microsoft Corporation,C=US (CA) | CN=DigiCert Global Root G2,OU=www.digicert.com,O=DigiCert Inc,C=US | 21 May 2025 | 19 Jun 2029 | RSA 4096 | SHA384-RSA | b0c6b2c466917b04773c647d4afc0c8 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of airaptr-api.azurewebsites.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| net. | present | 37331 | 13 | Verified |
| azurewebsites.net. | absent | 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 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://airaptr-api.azurewebsites.net/names/mcp | Verified | 200 | |
| http (plaintext) | http://airaptr-api.azurewebsites.net/names/mcp | Inconclusive | 405 |
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 →
check_domain Check and price domain names ~85
Use when the user wants a domain name, is naming a business or project, or asks whether a domain is taken. Checks up to 20 full domain names (you can suggest variations and check them together) and returns whether each is available and its price.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Full domain names, e.g. ["getrapp.ai", "getrapp.com"] |
No output schema declared.
No examples provided.
check_names Check business names ~152
Use when someone is naming a business, startup, product, brand, app, side hustle, shop, podcast or project. Brainstorm candidate names first, then check up to 8 at once: for each, which domains (.com, .co, .ai, .io, .app by default) are free with prices, and whether the GitHub name is free. Results are ranked, a free .com counts most. Suggest new candidates and check again if the best ones are taken.
| Name | Type | Req | Description |
|---|---|---|---|
| endings | array | – | Optional domain endings to check, e.g. ["com", "shop"] |
| names | array | yes | Candidate names, e.g. ["Rise and Crumb", "Northwind Bakery"] |
No output schema declared.
No examples provided.
register_domain How to register a domain ~60
Use when the user wants to buy an available domain. Explains how to register it: AI agents pay per call; people ask us and we register it for them. Nothing is bought by this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to register |
No output schema declared.
No examples provided.
request_service Ask us to build something ~70
Use when the person wants something none of these tools can do and says yes to passing the request on. Records only the request text they agree to send (no name or contact). Ask before calling it.
| Name | Type | Req | Description |
|---|---|---|---|
| request | string | yes | What they want, in a sentence, as they agreed to send it |
No output schema declared.
No examples provided.
How do I install the io.github.kody-w/raptr-names MCP server?
io.github.kody-w/raptr-names is a hosted endpoint at https://airaptr-api.azurewebsites.net/names/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 · airaptr-api.azurewebsites.net
claude mcp add --transport http kody-w-raptr-names 'https://airaptr-api.azurewebsites.net/names/mcp'
What is the io.github.kody-w/raptr-names MCP server?
io.github.kody-w/raptr-names is an MCP server listed in the public MCP registry as io.github.kody-w/raptr-names. Name a business or project; check which domains and GitHub names are free, with prices. This page covers its hosted endpoint (https://airaptr-api.azurewebsites.net/names/mcp).
Is the io.github.kody-w/raptr-names MCP server safe to use?
io.github.kody-w/raptr-names scores 71 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.kody-w/raptr-names MCP server expose?
io.github.kody-w/raptr-names exposes 4 tools: check_domain, check_names, register_domain, request_service. Their descriptions and schemas cost roughly 367 tokens of context every time the server is loaded.
Does the io.github.kody-w/raptr-names MCP server require authentication?
No. We connected to io.github.kody-w/raptr-names without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.kody-w/raptr-names MCP server still maintained?
io.github.kody-w/raptr-names is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.