Todo MCP
REMOTE · 343E-2405-201-303A-4980-A1C1-6538-33C0-A7D8.NGROK-FREE.APP · SCANNED AUG 24
Create, list, and complete todo items through MCP.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 4 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Todo MCP server?
Todo MCP is a hosted endpoint at https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/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 · 343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app
claude mcp add --transport http ankitpat-todo-mcp 'https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp'
{
"mcpServers": {
"ankitpat-todo-mcp": {
"url": "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp"
}
}
} {
"servers": {
"ankitpat-todo-mcp": {
"type": "http",
"url": "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp"
}
}
} [mcp_servers.ankitpat-todo-mcp] url = "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ankitpat-todo-mcp": {
"type": "remote",
"url": "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp",
"enabled": true
}
}
} openclaw mcp add ankitpat-todo-mcp --url 'https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp' --transport streamable-http
mcp_servers:
ankitpat-todo-mcp:
url: "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp" {
"McpServers": {
"ankitpat-todo-mcp": {
"Transport": "http",
"Url": "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp"
}
}
} assistant mcp add ankitpat-todo-mcp -t streamable-http -u 'https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp'
{
"mcpServers": {
"ankitpat-todo-mcp": {
"type": "http",
"url": "https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Aug 26 −40
- Endpoint reachability: reachable → not serving MCP ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 18 Aug 26 63
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 24 Aug 2026 · Probed https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.ngrok-free.app | CN=YE2,O=Let's Encrypt,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 575d5b4abbc36bfb93752d3ad60184c6c6d |
| SANs: *.ngrok-free.app, ngrok-free.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
DNSSEC insecure
Validation of 343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| ngrok-free.app. | 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 | 404 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp | HTTPS enforced | 307 | https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp |
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.
complete_todo Complete Todo ~26
Mark an existing todo as completed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The todo ID |
No output schema declared.
No examples provided.
create_todo Create Todo ~35
Create a new todo item.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Optional todo description |
| title | string | yes | The todo title |
No output schema declared.
No examples provided.
get_todos Get Todos ~33
Get all todo items, optionally including completed todos.
| Name | Type | Req | Description |
|---|---|---|---|
| includeCompleted | boolean | – | Whether completed todos should be included |
No output schema declared.
No examples provided.
What is the Todo MCP server?
Todo MCP is listed in the public MCP registry as io.github.AnkitPat/todo-mcp. Create, list, and complete todo items through MCP. This page covers its hosted endpoint (https://343e-2405-201-303a-4980-a1c1-6538-33c0-a7d8.ngrok-free.app/mcp).
Is the Todo MCP server safe to use?
Todo MCP scores 23 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 Todo MCP server expose?
Todo MCP exposes 3 tools: create_todo, get_todos, complete_todo. Their descriptions and schemas cost roughly 94 tokens of context every time the server is loaded.
Does the Todo MCP server require authentication?
No. We connected to Todo MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Todo MCP server still maintained?
Todo MCP is still listed as active in the MCP registry. We last reached this channel on 24 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.