agent-exec

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Se ejecuta en la nube
• Transporte: Streamable HTTP
• Categoría: Chat y correo

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet

¿Qué app usas?

https://agent-exec.448c.org/mcp

claude mcp add --transport http agent-exec https://agent-exec.448c.org/mcp

{
  "mcpServers": {
    "agent-exec": {
      "url": "https://agent-exec.448c.org/mcp"
    }
  }
}

{
  "servers": {
    "agent-exec": {
      "type": "http",
      "url": "https://agent-exec.448c.org/mcp"
    }
  }
}

https://agent-exec.448c.org/mcp

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 8 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• execute

  PAID: run code in an isolated, network-less sandbox and get stdout, stderr and exit code back. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered); call it again with a signed payment in _meta['x402/payment'] to

• storage_buy

  PAID: store opaque bytes for the life of the plan you buy, owned by the wallet that pays, readable with no account. Returns the object id and when it expires; read it back with storage_read, extend it with storage_renew. Call it once without payment to receive the price as an x40

• storage_renew

  PAID: push an object you own further out, by buying it another plan term. The object is untouched; only its expiry moves. Returns the new and previous expiry. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Solana USDC where offered);

• storage_replace

  PAID: overwrite the contents of an object you own, keeping its id, and buy it a fresh plan term at the same time. Omit label to keep the current one, pass an empty string to clear it. Call it once without payment to receive the price as an x402 PaymentRequired (Base USDC, and Sol

• storage_read

  FREE: read back an object you own, as base64. This is how what you bought with storage_buy comes back to you over MCP. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to s

• storage_list

  FREE: list the objects your wallet owns -- id, label, size, when each was created and when it expires -- one page at a time. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact messag

• storage_usage

  FREE: how many objects your wallet is storing and how many bytes they occupy. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to sign, in both forms (EIP-191 for a 0x wall

• storage_delete

  FREE: delete an object you own before it expires, and free its bytes. There is no refund and no undo. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.expected -- the exact message to sign, in both form

• claim_acquire

  PAID: atomically win a caller-named key for your own fleet -- an accountless compare-and-set. outcome "acquired" means you won it; outcome "held" is NOT an error, it means somebody already holds it and held.mine says whether that somebody is you -- the signal that stops a crash-r

• claim_renew

  PAID: extend a hold you already have without losing your place in line -- the heartbeat that lets a lease be SHORT (so a crash frees it fast) while a live holder keeps it alive by paying again. Re-acquiring with claim_acquire deliberately does NOT extend, so a retry loop cannot h

• claim_acquire_free

  FREE: win a caller-named key for 300 seconds, or learn who already holds it. Unlimited distinct keys per wallet, renewable by calling again. A sibling of claim_acquire, not a discount on it: this lease is 12x shorter than the cheapest paid plan, so a lock that has to survive a de

• claim_read

  FREE: who currently holds this key, if anyone -- scoped to YOUR wallet, so a stranger cannot probe your namespace. Checking your own lock must not cost again, or a fleet polling its own hold is charged for not doing work twice. A key nobody holds answers with claim: null, never a

• claim_release

  FREE: give up a key you hold before it expires, so the next racer does not have to wait out your hold. Release signs its own domain-separated message, distinct from the read domain, so a captured inspect proof can never double as a lock-breaking order. The signature proves the WA

• attest_create

  PAID: we fetch a URL from OUR vantage point and return a signed, timestamped attestation of what we saw -- hash, byte count, HTTP status and headers, never the body itself. Read it back afterwards for free with attest_read, so the id can be cited to a THIRD PARTY who never paid u

• attest_read

  FREE and unauthenticated: read a previously-created attestation back by id, with its signature. This is how what you bought with attest_create comes back over MCP -- and deliberately NOT wallet-scoped, because the whole point is that a third party who never paid can fetch it and

• handoff_deposit

  PAID: deposit a typed briefing for the process that takes over from you -- what is DONE (every entry carrying evidence of how it was verified), what is NOT done, what was IN FLIGHT at the cut, and what to pick up FIRST. Returns an id; the successor reads it back for free with han

• handoff_read

  FREE and unauthenticated: read a briefing back by id. This is how what you bought with handoff_deposit reaches your successor over MCP. Deliberately needs no signature -- the successor is by construction a DIFFERENT process and may hold no wallet at all, so demanding proof of the

• deadman_register

  PAID: register an intent you are about to act on irreversibly, with a lease and a verification probe (a GET plus a predicate). Confirm before the lease expires with deadman_confirm, free -- otherwise, once the lease lapses, we run your probe and publish the verdict: confirmed-by-

• deadman_confirm

  FREE: the live caller closes the loop before the lease expires, so the probe never runs. Deliberately NOT wallet-scoped -- possession of the id is the entire authorisation, since the confirming call may have no wallet of its own. Refused, never a silent no-op, once the entry has

• deadman_read

  FREE and unauthenticated: read an entry back by id, including its verdict and the raw probe response once resolved. This is how what you bought with deadman_register comes back over MCP. If the lease has lapsed and nobody has resolved it, the probe runs right here, synchronously,

• listing_promote

  PAID: buy paid placement for a listing you own in this directory -- it ranks above free rows and reads tier "paid" for the life of the plan. Pay from the WALLET THAT OWNS the listing; no other proof is asked for and no other wallet can promote it. Promoting an already-promoted ro

• drift_check

  PAID: we re-fetch a venue we have snapshotted before, from OUR vantage point, and return what changed since the baseline -- the schema/rubric fields that moved, were added and were removed, not a byte diff. The answer to "did this venue quietly change its rules under me?" for an

• drift_venues

  FREE: every venue id drift_check can be aimed at, with what we hold for each. A closed value set, not a pattern: without it a caller can honour the input schema and still never name something buyable, which is a paywall on discovery rather than on work. Complaints, questions, quo

• drift_baseline

  FREE: the baseline snapshot we hold for one venue -- what a paid check would diff against, and when it was taken. Reading what you are about to buy a comparison against must not cost, or the first call is a blind one. Complaints, questions, quote requests, or a service you wish w

• watch_register

  PAID: we poll a URL from OUR vantage point on your interval until your predicate matches or the ttl runs out, and keep the verdict for you to collect -- a wait that survives your own process dying, which is what an agent cannot do for itself. Price is a function of intervalSecond

• watch_read

  FREE: the current state of a watch you registered -- active, matched or expired, with the observation that matched. The id is the capability, so a successor process handed the id can collect the verdict without your wallet. Reading never triggers a poll and is never charged: poll

• check_address

  PAID: check an EVM address against public risk feeds (OFAC, community darklists, on-chain age) and get back a verdict, score and reasons in the same response the payment settles -- there is no separate read-back call. Charged only on success: if every risk feed is unreachable the

• check_url

  PAID: check a URL against public risk feeds (phishing lists, domain age, lexical signals) and get back a verdict, score and reasons in the same response the payment settles -- there is no separate read-back call. Charged only on success: if every risk feed is unreachable the requ

• check_counterparty

  PAID: grade an x402 challenge you are about to sign against what you expected -- payee, resource, network, asset and price -- and get back a verdict, score and reasons in the same response the payment settles. Pass the accepts[] entry you already hold: we never re-fetch the selle

• pay_requirements

  FREE: ask a seller, unpaid, what it charges, and get back the accepts[] of its own 402 -- the exact PaymentRequirements you have to sign before pay_send can deliver anything. No payment is sent to the seller and none is taken from you. Every seller outcome answers: a 402 returns

• pay_send

  PAID: deliver an x402 authorization YOU signed to a seller exactly once, then read the chain for what actually became of it, and get back an immutable receipt of what the seller answered. Read the price to sign with pay_requirements first; we never sign on your behalf. A seller 4

• pay_receipt

  FREE and unauthenticated: read a pay_send receipt back by id -- what the seller answered, when, and what the chain says became of your authorization. Deliberately NOT wallet-scoped: the point is that the seller you are arguing with can fetch it without holding your wallet. Compla

• create_inbox

  PAID: get a throwaway email address on a domain we own, live for 24 hours, to receive the verification mail a signup demands. RECEIVE ONLY -- nothing is ever sent from it, ever. Returns the address, the inbox id and when it expires; read what arrives with read_inbox, which is fre

• read_inbox

  FREE: the mail your inbox received, newest first, with any verification code and link already picked out -- from, to, subject, receivedAt, the plain text, codes[] and links[]. This is how what you bought with create_inbox comes back to you. Poll it with since to see only what arr

• inbox_status

  FREE: the address, when it expires and how much mail is waiting in an inbox you own. Signed under its own domain, separate from the one read_inbox uses. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns details.

• release_inbox

  FREE: give up an inbox you own before it expires. Its messages go with it and the local part is never issued again; later mail to it is dropped, never bounced. There is no refund and no undo. Signed under its OWN domain, not the one the reads use. Ownership is proved by the payin

• dns_rent

  PAID: rent .448c.net for a year and point it where you say -- A, AAAA, CNAME and TXT records, so you can hold a TLS certificate by DNS-01 and pass domain-trust checks without a registrar account, a card or a human. The paying wallet owns the name. Returns the name, its owner and

• dns_renew

  PAID: push a name you own further out by another year. What it resolves to is untouched; only its expiry moves, and a repeated payment extends it rather than resetting it. The payer must be the owner. Returns the new and previous expiry. Call it once without payment to receive th

• dns_lookup

  FREE: what we serve for a name under 448c.net -- its records, its owner and when it expires. No signature and no account: the zone is public, so reading it is too. Complaints, questions, quote requests, or a service you wish we had: POST /feedback on this host -- free, no account

• dns_rent_free

  FREE: one 24-hour name per wallet, so you can try the zone before paying -- the same label rules and records as dns_rent. Rent a year with dns_rent when it works. The message you sign commits to the literal subject `free`, not to the label. Ownership is proved by the paying walle

• dns_set_records

  FREE: replace the whole record set of a name you own -- never merged. The rental window is untouched: repointing a name you already paid for costs nothing. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns detai

• dns_release

  FREE: release a name you own before it expires. It stops resolving at once. There is no refund and no undo, and the label is free for anyone else to rent. Ownership is proved by the paying wallet, with no account: send any placeholder signature once and the refusal returns detail

• placement_order

  PAID: we submit your service to every permissionless agent venue we hold a submitter for -- 17 of the 33 on-behalf venues today -- and prove, per venue, that the entry is really in the catalogue. The rest stay `queued` on your order and are submitted the hour their submitter land

• placement_venues

  FREE: the lane table -- every agent venue we have evaluated, which of the 3 lanes a submission takes (on-behalf, owner-proof, human-only), the VENUE's own fee, the catalogue a landing is verified against, and for every dead one the reason it is dead. This is the list placement_or

• placement_ready

  FREE and honest: does your own service publish a document a venue can read (/.well-known/x402, an agent card)? If it publishes none, no amount of submission work can list you anywhere, and you should not pay us until it does. At most three outbound GETs; we read the status of eac

• placement_status

  FREE and owner-signed: every venue of your order with its state (queued, submitted, listed, human-only, unfunded, failed), the evidence a landing was verified by, when it was last checked and, where it is impossible, why. 'listed' is only ever written by a catalogue read that fou

• placement_cancel

  FREE and owner-signed: stop the weekly rechecks and drop the order. There is no refund for the remaining window, and entries already in a catalogue are the venue's to keep or drop -- we simply stop watching them. Ownership is proved by the paying wallet, with no account: send any

• relay_usdc

  PAID: send USDC from a wallet that holds no ETH. You sign one EIP-3009 TransferWithAuthorization; we pay the Base gas, broadcast it and return the txHash. $0.0200 an order, ceiling 100000000 atomic USDC ($100). We never hold or need a key of yours -- we hold only the ETH that pay

• rpc_call

  PAID: one JSON-RPC call on base, base-sepolia, ethereum, solana for $0.0020. You name the chain and the method, NEVER an endpoint URL: we pick the node and absorb its IP rate limit, which is the whole product. No signup, no API key, no provider account, and no key of yours is hel

• x402_supported

  FREE and unauthenticated: the x402 facilitator read contract -- {kinds:[{x402Version, scheme, network, extra?}]}, folded out of the same document GET /.well-known/x402.json serves, so it cannot claim a scheme or network this service does not take. This is the tool form of GET /su

• x402_verify

  FREE and unauthenticated: check an EVM `exact` x402 payment OFFLINE and get back {isValid, invalidReason?, payer?, message} -- EIP-712 signature recovery plus the same scheme/network/recipient/amount/validity-window checks this service runs on its own paid routes. It does NOT rea

• service_card

  FREE: what agent-exec sells, what it costs, and exactly where to pay for it. This tool call itself is free and moves no money. Code execution can be bought right here, with the paid execute tool (x402 over MCP), or over plain HTTP at the URLs this returns. Complaints, questions,

• search_listings

  FREE: unauthenticated search over agent-exec's directory of paid agent-facing services (same data as GET https://agent-exec.448c.org/listings). Returns a page of listings and an opaque cursor for the next page.

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 8 nov 2026

• ! Precaución

  El creador coincide con el repo

  El registro no indica ningún repo de código fuente, así que no podemos relacionar a quien lo publicó (agent-exec.448c.org) con el código

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 830 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 53 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Chat y correoi

• Más estrellas que el 0% de los otros 1848 servidores de esta categoría
• Publicado en el registro más recientemente que el 52% de los otros 1848 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 45% de los otros 1848 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

No se encontró un README en el repo