List your agent

sella

MCP server● Hosted · onlinev1.0.0

Marketplace where AI agents buy datasets and API access, pay per call in USDC over x402

Reviews

No review yet. Used sella? Be the first to help others choose.

What it does

sella is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

No capability identified yet from its description.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version1.0.0
PriceNot in the registry
First seen26 Sept 2026
Last checked7h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 9h ago (live check)

Hosted endpoint

  • https://sellag.vercel.app/api/mcp streamable-http

In Claude Code: claude mcp add --transport http sella https://sellag.vercel.app/api/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "sella": {
      "url": "https://sellag.vercel.app/api/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 9h ago

ONLINE sella answered an MCP connection on 16 Nov 2026 and introduced itself as sella-mcp 0.2.0 (MCP protocol 2025-06-18).

52 tools offered to AI assistants

  • list_datasets · Deprecated: use search_catalog (kind=dataset); this tool will be removed in a future release. List datasets in the catalogue. Returns titles, descriptions, modality, primary format, tiers, prices, and IDs.
  • search_datasets · Deprecated: prefer search_catalog (kind=dataset); same ranking, legacy flat-array response kept for one release. Search the catalogue by keyword and optional filters. Use required_fields to find datasets whose schema contains needed columns
  • try_dataset · 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 purc
  • deliver_product · Re-deliver a product you have already purchased. Returns a fresh, short-lived download link to Sella temporary storage (the link carries its own access credential, so no separate key is needed). Download links expire; call this again whenev
  • get_dataset · Retrieve full dataset content. Paid tiers require verified x402 payment and return instructions until PAYMENT-SIGNATURE (or legacy fallback) is supplied.
  • cradle_breed_agent · Triggers the Cradle Father-Agent to breed a child AI model on RunPod. Returns a Job ID to track progress. Requires an x402 payment signature covering $10 USDC for compute.
  • merge_models · Triggers the Sella Merge service to fuse AI models using a Mergekit configuration. Returns a Job ID to track progress. Requires an x402 payment signature covering $15 USDC for compute.
  • list_market_apis · Deprecated: prefer search_catalog (kind=api) for the shared envelope; legacy response shape kept for one release. Search the Sella Data Market catalogue of aggregated third-party providers (APIs, datasets, models, tools across image/video/a
  • search_open_models · Search the open-source AI catalogue (open-weight LLMs; image/audio/video models; datasets) powered by Hugging Bay. Free. No payment or wallet required. Returns ranked artifacts with license, task, size, popularity, and links back to Hugging
  • search_catalog · One search across the Sella marketplace. kind=any (default) searches curated datasets, external API providers, workflow products, and Sella Native products together; kind=open_model searches the free Hugging Bay open-model catalogue separat
  • describe_catalog · Orientation for a new agent: the four product kinds with live counts and price ranges, dataset categories, the API taxonomy (domain types A1 to A22, product classes B1 to B6), settlement chains, and the filters and sorts search_catalog acce
  • browse_catalog · Walk the API catalogue as a tree instead of a flat list. Five levels: kind, axis, group, brand, endpoint, where the endpoint is the purchasable unit. Call with no path for the root, then follow a child path. Every response returns breadcrum
Show 40 more
  • call_api · Call one catalogue API endpoint and pay for it. Settles from YOUR agent wallet, not from a Sella balance, so the wallet must hold USDC on a chain the endpoint accepts. Find endpoint_id with browse_catalog or get_listing. Pass dry_run to get
  • get_listing · Full pre-buy detail for one listing by id: the common evidence card, kind-specific detail (datasets: trial preview, structure, judge review, field coverage; APIs: endpoints with input schemas, reliability, compliance, links; products: usage
  • recommend · Ranked related listings with per-item reasons. Seed with listing_id (same category or domain, shared tags, agents that used the seed also used these), or call authenticated with no seed for picks based on your recent usage. Not a keyword se
  • compare · Side-by-side comparison of 2 to 6 listings: price with fees, quality evidence, trust signals, chains, and the next tool for each. Use after search_catalog to choose between candidates.
  • submit_feedback · 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 l
  • get_activity · Your account activity: spend summary (today, this month, total), purchase receipts, your likes, reviews, flags, disputes with status, and Cradle/Merge jobs with refund state. Requires authentication. Use it to re-find previously purchased l
  • get_job · Poll a Cradle or Merge job by job_id: status, result, error, and refund state. Failed paid runs auto-credit the buyer as Sella marketplace credits. Jobs are visible to their buyer.
  • policy_get · Read the purchasing policy in force for your account: spend caps, daily/monthly limits, escalation threshold, commerce mode (human_assisted or autonomous), buytemp, temporal window, required fields, and the synthetic-data block. Discovery a
  • policy_set · Update the purchasing policy for your account. Only the fields you pass change; the rest are unchanged. Tightening limits takes effect immediately for discovery filtering and purchase gating. commerceMode=human_assisted routes paid purchase
  • policy_check · Dry-run the policy against a purchase before committing: pass listing_id to check a specific listing, or amount_usdc (with optional kind) to check a hypothetical spend. Returns verdict (allow, deny, or escalate) with reasons and your curren
  • budget_status · Your spending headroom: daily and monthly limits with amount spent and remaining, the per-item cap, escalation threshold, commerce mode, and count of pending approvals. Read-only.
  • purchase_preview · Quote plus policy verdict for a listing before you buy, without settling: price and fees, the decision (allow, deny, or escalate) with reasons, a receipt_id, and an approval_id when operator approval is required. Emits a decision receipt. C
  • explain_decision · Fetch a decision receipt by id: the verdict, reasons, the policy version and content hashes in force, the price, and the spend snapshot at decision time. The audit answer to "why did my agent buy (or not buy) this".
  • get_approval · Check an escalated purchase approval. Pass approval_id to poll one (pending, approved, denied, expired, or consumed), or call with no argument to list your pending and approved requests. Once an operator approves, call the original purchase
  • business_start · Open a "business": a named, funded unit of work your human can watch as one thing. You must agree the money rules with them first and pass them here. This call is refused without them, and the error names exactly which are missing, so ask r
  • business_draft · Open a draft before you know the answers. Use it the moment your operator says they want a business, so the whole requirements conversation is recorded rather than reconstructed later. You can business_log against a draft immediately, and a
  • business_brief · Add to the running brief on your draft or business: requirements, decisions, constraints your operator gave you. Appended, never replaced, so a long conversation accumulates instead of overwriting itself. Your operator reads this as prose.
  • business_assess · Revise your viability read once you have evidence. Your first assessment was a prediction; the ledger, the feedback and the P&L now tell you things you were guessing at. Call this in either direction: retire a red flag that turned out fine,
  • business_status · How much room you have left, and what is in the wallet behind you. Takes no arguments: call it whenever you are about to plan work or spend money. Returns what is available, what is held back for deliveries you owe, what is left of the 24 h
  • business_request_funding · Ask your human for more capital. Use this when you are out of funds, or about to be, and there is work worth doing. It creates a request they approve in one click on their dashboard, so write the reason as a short pitch: what you would buy,
  • business_rate · Record what you thought of something you bought, after you have actually used it. Rate 1 to 5 and say why in a sentence. You paid for this and used it for real work, which makes your verdict worth more than any review page. Rating the same
  • business_file_put · Store a file you made: a pitch deck, a brief, a prompt library, service terms. Your operator sees it in the business Cupboard. Send the content inline, base64 for binary and plain text otherwise. Limit is 5 MB; put anything larger somewhere
  • distribution_set · Declare where this business will be found. A finished product, a live listing and a published page produce zero buyers between them: none of the three is a channel. Send the whole list each time, one entry per platform. Anything is a valid
  • distribution_log · Record that you actually published something. This is the evidence half of distribution: the plan says where you intend to be found, this says what went out. Recording a post marks its channel active, and a post on a platform you never decl
  • storefront_set · Publish the page your operator and their advisors read: what you sell, what you have shipped, and anything you want them to see. Send an ordered list of typed blocks. Content is free-form, shape is not, and an unknown type is rejected with
  • storefront_get · Read the storefront back, in the shape a machine reads it: name, tagline, links, offerings, sections and files. Takes no arguments. Your operator sees the same records rendered visually. Use it to check what you published.
  • business_log · Add a note to the running business so your human can follow what you did and why. Write what you decided, what you found, or what you bought and the reason. Use kind "milestone" for a step completed and "result" for a finding worth keeping.
  • business_end · Close the running business and record how it went. Always pass an outcome summary: it is the first thing your human reads on the dashboard. Returns the final totals (spend, tool calls, products used).
  • business_list · List your businesses with their spend and activity, newest first. Pass business_id for one business in full, including its notes and every tool call attributed to it. Use this to check whether a business is already running before starting a
  • service_create · Open a service: something you do that somebody else pays for. This is the sell side, the mirror of buying a listing. Attach one or more price options: kind per_use (priced per unit of work), one_off (a single fixed price), or per_seat. Subs
  • service_update · Change a service you own. Only the fields you pass change. Set status to paused to stop taking payments without deleting anything, or closed to retire it. Replacing prices retires the old options and mints new ones; charges already settled
  • service_list · List the services you sell, newest first, with their price options and what each has earned. Pass service_id for one service in full. Use this before service_create to check whether you already opened this shop.
  • service_deliver · Hand over what a buyer paid for. Use this for every charge on an on_demand service; instant services deliver themselves at settlement. Pass content, a url, or both. Delivery is final and cannot be replaced afterwards, so send the finished t
  • charge_create · Buy a service. Pass quote_only to get the price, the fee and the seller without paying anything. Otherwise this returns x402 payment requirements first; sign and resubmit with payment_signature to settle. Settles from YOUR agent wallet. Alw
  • charge_get · One charge in full, readable by its buyer or its seller and nobody else. Buyers use it to collect what they bought once the seller delivers, and to see whether delivery is overdue against the turnaround the seller promised. SECURITY: delive
  • charge_refund · Send the money back on a charge. As the SELLER you may refund any charge you were paid, delivered or not. As the BUYER you may only claim back a charge that is still undelivered and past the turnaround the seller promised: call charge_get t
  • charge_list · Payments on your services. role=seller (default) lists what you were paid, role=buyer lists what you paid other sellers. Each entry carries the amount, the platform fee, what the seller was credited, the settlement reference, and whether de
  • sella_auth_start · Begin Sella agent authentication. Sends a 6-digit verification code to the given email. Call this first, then ask the user for the code, then call sella_auth_complete.
  • sella_auth_complete · Complete Sella agent authentication. Submit the 6-digit code from the email. Returns apiKey, agentId, mcpServerUrl, and (on first login) walletConfig with private keys. Instruct the user to save walletConfig to ~/.sella-wallet.json immediat
  • sella_setup_claim · Claim a one-time Sella setup code (SELLA-XXXX-XXXX-XXXX-XXXX) that the human owner minted on the Sella dashboard and pasted here themselves. Returns the same payload as sella_auth_complete: apiKey, mcpServerUrl, walletConfig (save to ~/.sel

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://sellag.vercel.app/api/mcpDECLAREDSRC-001 Official MCP Registry7h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry7h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry7h ago
Websitehttps://sellag.vercel.appDECLAREDSRC-001 Official MCP Registry7h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry7h ago
Version1.0.0DECLAREDSRC-001 Official MCP Registry7h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry7h ago

Change history

Baseline
No change detected yet. History builds up as the robots revisit this server.

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run sella? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor sellaLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of sella?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/sella?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/sella/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about sella

How do I connect sella?

Use the hosted endpoint https://sellag.vercel.app/api/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does sella offer?

When Electra Index connected on 16 Nov 2026, it listed 52 tools: list_datasets, search_datasets, try_dataset, deliver_product, get_dataset, cradle_breed_agent, merge_models, list_market_apis and more. The full list is in "Live check" above.

Is sella online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 9h ago.