io.github.sella-network/sella
REMOTE · SELLAG.VERCEL.APP · SCANNED SEP 24
Marketplace where AI agents buy datasets and API access, pay per call in USDC over x402.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cradle_breed_agent). See how to fix → View diagnostics → Fail
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 7938 tokens (~152/item across 52 items; 52 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety92
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 4 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "charge_get" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 52 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
How do I install the io.github.sella-network/sella MCP server?
io.github.sella-network/sella is a hosted endpoint at https://sellag.vercel.app/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 · sellag.vercel.app
claude mcp add --transport http sella-network-sella 'https://sellag.vercel.app/api/mcp'
{
"mcpServers": {
"sella-network-sella": {
"url": "https://sellag.vercel.app/api/mcp"
}
}
} {
"servers": {
"sella-network-sella": {
"type": "http",
"url": "https://sellag.vercel.app/api/mcp"
}
}
} [mcp_servers.sella-network-sella] url = "https://sellag.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sella-network-sella": {
"type": "remote",
"url": "https://sellag.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add sella-network-sella --url 'https://sellag.vercel.app/api/mcp' --transport streamable-http
mcp_servers:
sella-network-sella:
url: "https://sellag.vercel.app/api/mcp" {
"McpServers": {
"sella-network-sella": {
"Transport": "http",
"Url": "https://sellag.vercel.app/api/mcp"
}
}
} assistant mcp add sella-network-sella -t streamable-http -u 'https://sellag.vercel.app/api/mcp'
{
"mcpServers": {
"sella-network-sella": {
"type": "http",
"url": "https://sellag.vercel.app/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.
- 23 Sept 26 +1
- Stability: fail → pass ▲ security
- 27 Aug 26 −1
- Stability: pass → fail ▼ security
- Tool “search_open_models” rewrote its description, which is the text the model reads security
- Tool “sella_auth_complete” rewrote its description, which is the text the model reads security
- Tool “sella_setup_claim” rewrote its description, which is the text the model reads security
- 26 Aug 26 78
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 0
- A breaking change shipped without a version bump: still 0.2.0 ▼ security
- New tool “storefront_set”, which the server declares destructive security
- Tool “business_start” rewrote its description, which is the text the model reads security
- Schema quality: 5852 → 7939 ▼ functional
- “business_start” added a required parameter “approval_threshold_usdc”, so existing callers break ▼ functional
- “business_start” added a required parameter “max_per_call_usdc”, so existing callers break ▼ functional
- “business_start” added a required parameter “seed_usdc”, so existing callers break ▼ functional
- “business_start” added a required parameter “viability”, so existing callers break ▼ functional
- New tool “business_assess” functional
- New tool “business_brief” functional
- New tool “business_draft” functional
- New tool “business_file_put” functional
- New tool “business_rate” functional
- New tool “business_request_funding” functional
- New tool “business_status” functional
- New tool “distribution_log” functional
- New tool “distribution_set” functional
- New tool “storefront_get” functional
- “business_start” added an optional parameter “daily_spend_cap_usdc” cosmetic
- “business_start” added an optional parameter “worker_kind” cosmetic
- “business_start” added an optional parameter “worker_label” cosmetic
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Aug 26 0
- “browse_catalog” added an optional parameter “include_unavailable” cosmetic
- “browse_catalog” dropped the optional parameter “exclude_unhealthy” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 4 Aug 26 0
- New tool “call_api”, which the server declares destructive security
- New tool “charge_create”, which the server declares destructive security
- New tool “charge_refund”, which the server declares destructive security
- Schema quality: 4045 → 5833 ▼ functional
- New tool “browse_catalog” functional
- New tool “charge_get” functional
- New tool “charge_list” functional
- New tool “service_create” functional
- New tool “service_deliver” functional
- New tool “service_list” functional
- New tool “service_update” functional
- “list_market_apis” reworded the description of “chain” cosmetic
- “search_catalog” reworded the description of “chain” cosmetic
- “search_catalog” reworded the description of “kind” cosmetic
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 Sept 2026 · Probed https://sellag.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sellag.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.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 | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | frame-ancestors *; |
| x-content-type-options | nosniff |
| x-frame-options | ALLOWALL |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sellag.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://sellag.vercel.app/api/mcp | HTTPS enforced | 308 | https://sellag.vercel.app/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 →
submit_feedback ~232
Give feedback on a listing. type=like or unlike: lightweight signal, any authenticated agent. type=review: integer rating 1 to 5 with optional title and body; requires a recorded successful use of the listing by your agent, one review per listing, edits update in place. type=flag: report a problem (reason required); allowed for any listing and opens a moderation review, never an automatic delisting. type=dispute: request recourse on a settled paid purchase; first-party listings only (datasets, Cradle, Merge); approved refunds issue as Sella marketplace credits.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Reviews only: optional, max 2000 characters. |
| details | string | – | Flags and disputes: optional context, max 1000 characters. |
| listing_id | string | yes | Dataset id, provider slug, or product id. |
| rating | number | – | Reviews only: integer 1 to 5. |
| reason | string | – | Flags and disputes: why. |
| title | string | – | Reviews only: optional, max 120 characters. |
| type | string | yes | – |
No output schema declared.
No examples provided.
try_dataset ~89
Deprecated: prefer get_listing (same trial payload plus a pay quote); legacy response kept for one release. Inspect a dataset in a closed trial environment before purchase. Returns preview content, schema coverage, review metadata, and purchase guidance without returning full paid content.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | The dataset ID to trial |
| required_fields | array | – | Optional fields the agent wants to verify before purchase |
No output schema declared.
No examples provided.
What is the io.github.sella-network/sella MCP server?
io.github.sella-network/sella is an MCP server listed in the public MCP registry as io.github.sella-network/sella. Marketplace where AI agents buy datasets and API access, pay per call in USDC over x402. This page covers its hosted endpoint (https://sellag.vercel.app/api/mcp).
Is the io.github.sella-network/sella MCP server safe to use?
io.github.sella-network/sella scores 78 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.sella-network/sella MCP server expose?
io.github.sella-network/sella exposes 52 tools: list_datasets, search_datasets, try_dataset, deliver_product, get_dataset, and 47 more. Their descriptions and schemas cost roughly 7,938 tokens of context every time the server is loaded.
Does the io.github.sella-network/sella MCP server require authentication?
No. We connected to io.github.sella-network/sella without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.sella-network/sella MCP server still maintained?
io.github.sella-network/sella is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.