1lev1
REMOTE · API.1LEV1.COM · SCANNED SEP 22
Track partnership work, log mission hours, and see what needs your approval on 1lev1.com.
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 → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 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. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the 1lev1 MCP server?
1lev1 is a hosted endpoint at https://api.1lev1.com/api/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 · api.1lev1.com
claude mcp add --transport http avi-adam-1lev1 'https://api.1lev1.com/api/mcp'
{
"mcpServers": {
"avi-adam-1lev1": {
"url": "https://api.1lev1.com/api/mcp"
}
}
} {
"servers": {
"avi-adam-1lev1": {
"type": "http",
"url": "https://api.1lev1.com/api/mcp"
}
}
} [mcp_servers.avi-adam-1lev1] url = "https://api.1lev1.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"avi-adam-1lev1": {
"type": "remote",
"url": "https://api.1lev1.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add avi-adam-1lev1 --url 'https://api.1lev1.com/api/mcp' --transport streamable-http
mcp_servers:
avi-adam-1lev1:
url: "https://api.1lev1.com/api/mcp" {
"McpServers": {
"avi-adam-1lev1": {
"Transport": "http",
"Url": "https://api.1lev1.com/api/mcp"
}
}
} assistant mcp add avi-adam-1lev1 -t streamable-http -u 'https://api.1lev1.com/api/mcp'
{
"mcpServers": {
"avi-adam-1lev1": {
"type": "http",
"url": "https://api.1lev1.com/api/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.
- 16 Sept 26 +2
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- 14 Sept 26 −34
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: 0.30 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 13 Sept 26 +35
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.30 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 12 Sept 26 −34
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.23 → unverified ▼ security
- Tool safety: pass → unverified ▼ 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
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +33
- Injection markers: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Schema quality: 26 → 39 ▼ functional
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.20 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- New tool “createNewApiKey” functional
- 8 Sept 26 −32
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.10 → unverified ▼ security
- Tool safety: pass → unverified ▼ 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
- 7 Sept 26 +10
- Transport: fail → pass ▲ security
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 22 Sept 2026 · Probed https://api.1lev1.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.1lev1.com | CN=YE2,O=Let's Encrypt,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5b15f5ce9e424c234ae3da27b5422947ea2 |
| SANs: api.1lev1.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.1lev1.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| 1lev1.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://api.1lev1.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://api.1lev1.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(self), microphone=(), camera=() |
| www-authenticate | Bearer resource_metadata="https://api.1lev1.com/.well-known/oauth-protected-resource" |
Protected resource metadata
| Document | https://api.1lev1.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.1lev1.com/api/mcp |
| Authorisation server | https://api.1lev1.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.1lev1.com/api/mcp | Auth required | 401 | |
| http (plaintext) | http://api.1lev1.com/api/mcp | HTTPS enforced | 301 | https://api.1lev1.com/api/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. 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 →
createNewApiKey ~66
Get a NEW 1lev1 API key: the exact command to run (npx 1lev1-mcp) and the approval URL. Also lists the stale config entries that must be deleted first, otherwise the new key is shadowed and nothing changes after a restart.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
getPlatformInfo ~26
Get general information about the 1lev1 platform, its goals, and features.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
howToConnect ~26
Instructions on how to register, login and get an API key for full MCP access.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the 1lev1 MCP server?
1lev1 is an MCP server listed in the public MCP registry as io.github.Avi-ADAM/1lev1. Track partnership work, log mission hours, and see what needs your approval on 1lev1.com. This page covers its hosted endpoint (https://api.1lev1.com/api/mcp).
Is the 1lev1 MCP server safe to use?
1lev1 scores 38 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 1lev1 MCP server expose?
1lev1 exposes 3 tools: getPlatformInfo, howToConnect, createNewApiKey. Their descriptions and schemas cost roughly 118 tokens of context every time the server is loaded.
Does the 1lev1 MCP server require authentication?
Yes. 1lev1 asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the 1lev1 MCP server still maintained?
1lev1 is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.