_ registry / mcp streamable-http · checked 2h ago

agentstack

https://agentstack.tech

Registry code: 5f7a821c598cd7d5

api record

AgentStack MCP — one tool: agentstack.execute (POST /mcp). Bound project: agents.work_next (recipe mcp_work_loop_v1) before catalog search. discovery.search is fallback only. Authenticate first: GPT/Cursor OAuth Connect (user logs in), or POST /mcp/.well-known/oauth-token grant_type=password, or MCP auth.login. If this client cannot complete OAuth, use the user's API key: header X-API-Key or Authorization: Bearer <user API key> from the profile. Session probe: auth.get_profile (alias auth.me). Bind context.project_id, then agents.work_next. Work Graph skill:…

endpoint
https://agentstack.tech/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is agentstack live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is agentstack free to use?
Not measured yet.
What tools does agentstack have?
1 tool: agentstack.execute.
Is agentstack safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
300ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 1 tools
1 never probed 0 of 1 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • agentstack.execute unknown never probed

    AgentStack MCP = Work Graph control plane. After session + context.project_id: agents.work_next (mcp_work_loop_v1) -> plan_claim -> plan_execute (CAS/leases). Follow packet.next_action; catalog/discovery.search only if no packet. One-shot CRM/upload may call domain actions directly. Spine: agents.plan_get -> agents.work_next -> agents.plan_claim -> agents.plan_execute. Cheap and batchable on one sync execute: agents.work_next, agents.plan_get, agents.plan_claim. One per sync execute: agents.plan_propose, agents.plan_apply_proposal, agents.plan_recovery_scan, context.get. Anti-pattern: Do not pick tools from catalog when packet.next_action is present. Mandatory session order: authenticate -> session probe auth.get_profile (alias auth.me) -> select/create project -> set context.project_id on every batch -> Work Graph loop. Playbook GET /mcp/prompts/get?name=agentstack_session_setup (recipe mcp_session_setup). Sync POST /mcp is lane mcp_batch (60000 ms) for the whole batch - not an RBAC cap. One expensive step per sync execute (bots.simulate, commerce.ai.generate_products, commerce.ai.magic_fill, knowledge.playground; agents.run with wait=true; agents.plan_suggest_tree when use_llm; agents.plan_apply_proposal, agents.plan_propose, agents.plan_recovery_scan, context.get). agents.work_next, agents.plan_get, and agents.plan_claim are cheap and may share that batch. LLM-heavy steps widen to ai_stream (180000 ms). Large suites: options.async=true then poll discovery.job_status (REST GET /mcp/jobs/{job_id}). Cite catalog_actions_public from GET /mcp/actions/summary. There is one execute tool (agentstack.execute); do not quote tools_count as 'N tools'. Do not invent rules.* or webhooks.* (prefer logic.* and integrations.*).

    mcp-tool

    {
      "type": "object",
      "required": [
        "steps"
      ],
      "properties": {
        "steps": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "id",
              "action"
            ],
            "properties": {
              "id": {
                "type": "string",
                "description": "Step id unique within this batch. Referenced by options.observed."
              },
              "if": {
                "type": "object",
                "description": "Optional predicate. The step runs only when this condition matches.",
                "additionalProperties": true
              },
              "action": {
                "type": "string",
                "description": "Canonical dotted action id from GET /mcp/actions (example: auth.get_profile)."
              },
              "params": {
                "type": "object",
                "description": "Action arguments. Shape comes from discovery.describe for that action.",
                "additionalProperties": true
              }
            },
            "description": "One action invocation inside the batch."
          },
          "minItems": 1,
          "description": "Ordered steps. Cheap list/get may batch. At most one heavy LLM action (bots.simulate, knowledge.playground, …) per sync execute."
        },
        "context": {
          "type": "object",
          "properties": {
            "locale": {
              "type": "string",
              "description": "Optional. en, ru, pt, or BCP-47. Overrides this request and is not saved."
            },
            "user_id": {
              "type": "integer",
              "description": "Caller user id. Usually taken from the session; do not invent it."
            },
            "project_id": {
              "type": "integer",
              "description": "Tenant project id. Required for project-scoped actions."
            },
            "generation_env_uuid": {
              "type": "string",
              "description": "Sandbox generation anchor (env_uuid). Not a recipe input."
            }
          },
          "description": "Execute scope: set project_id on every batch; optional locale (en, ru, pt, or BCP-47) overrides this request and is not saved.",
          "additionalProperties": true
        },
        "options": {
          "type": "object",
          "properties": {
            "goal": {
              "type": "string",
              "description": "The same user goal. When set, the envelope names the next playbook step."
            },
            "async": {
              "type": "boolean",
              "description": "Queue the batch (durable job). Required for more than one heavy LLM step. Poll discovery.job_status or GET /mcp/jobs/{job_id}."
            },
            "density": {
              "enum": [
                "strict",
                "guided",
                "autonomous"
              ],
              "type": "string",
              "description": "Wording of the current step. The allowed action set stays the same."
            },
            "envelope": {
              "enum": [
                "compact",
                "full"
              ],
              "type": "string",
              "description": "Batch step payload shape. compact omits duplicate data/capability_result."
            },
            "observed": {
              "type": "object",
              "description": "Playbook progress. completed_steps holds step ids, not action names.",
              "additionalProperties": true
            },
            "recipe_id": {
              "type": "string",
              "description": "Expand a registered MCP recipe into steps before execute (see GET /mcp/recipes)."
            },
            "stopOnError": {
              "type": "boolean",
              "description": "Stop the batch at the first failed step. Default true."
            },
            "publish_asked": {
              "type": "boolean",
              "description": "The user already asked to publish. Skips a second confirm."
            },
            "recipe_params": {
              "type": "object",
              "description": "Values for {{placeholders}} in the recipe.",
              "additionalProperties": true
            },
            "continueOnError": {
              "type": "boolean",
              "description": "Keep later steps running after a failure. Opposite of stopOnError."
            },
            "idempotency_key": {
              "type": "string",
              "description": "Client retry key. The same key returns the same receipt."
            },
            "workflow_run_id": {
              "type": "string",
              "description": "Goal run id. Separate from trace_id. Returned on the completion receipt."
            },
            "enforce_approval": {
              "type": "boolean",
              "description": "When true, financial, destructive, and access-control steps pause for approval."
            },
            "semantic_contract": {
              "type": "object",
              "description": "Fingerprinted GoalSemanticContract — discovery/search parity for inverse batches.",
              "additionalProperties": true
            }
          },
          "description": "Batch controls: async jobs, recipes, playbook progress, and error policy.",
          "additionalProperties": true
        }
      },
      "description": "Batch execute. One tool; each step names a dotted action. Structured result fields: see tools/list outputSchema on agentstack.execute."
    }
    arguments 140 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5f7a821c598cd7d5.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5f7a821c598cd7d5/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5f7a821c598cd7d5/badge.svg)](https://brick.blue/agent/5f7a821c598cd7d5?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
50%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.