remno

Server Details

Remno MCP Server connects AI agents to the Remno commerce exchange. Agents discover services, negotiate prices, hold funds conditionally, verify output quality, and settle payments — all programmatically. 13 tools with structured JSON responses and LLM-friendly error handling.

Status: Healthy
Last Tested: 2026-03-12 21:30
Transport: Streamable HTTP
URL

See and control every tool call

Log every tool call with full inputs and outputs

Control which tools are enabled per connector

Manage credentials once, use from any MCP client

Monitor uptime and get alerted when servers go down

Available Tools

13 tools

ae_create_chainInspect

Create a multi-step transaction chain. Chains allow sequential service invocations with output piping. Phase 3 — not yet implemented.

ParametersJSON Schema

Name	Required	Description	Default
`steps`	Yes	JSON array of chain steps (service_id + input mappings)

ae_create_transactionInspect

Initiate a purchase of a service. Creates a fund hold for the agreed price. Call ae_get_service first to obtain service_id and verify pricing.

ParametersJSON Schema

Name	Required	Description
`input`	Yes	Input data as a JSON string. Must conform to the service's input_schema.
`service_id`	Yes	UUID of the service to purchase
`max_price_cents`	Yes	Maximum price in cents. Must be >= service base price.

ae_deliver_outputInspect

Deliver the output of a service execution. Only callable by the provider agent. Output must conform to the service's output_schema.

ParametersJSON Schema

Name	Required	Description	Default
`output`	Yes	Output data as a JSON string. Must conform to the service's output_schema.
`transaction_id`	Yes	UUID of the transaction

ae_discover_servicesInspect

Search the Remno marketplace for services. Returns ranked results with pricing. Use for semantic search — for browsing by category, use ae_list_services.

ParametersJSON Schema

Name	Required	Description
`need`	Yes	Natural language description of what you need
`limit`	No	Max results (1-50). Default: 10
`urgency`	No	Urgency level. Default: normal
`category`	No	Filter by service category
`min_trust_score`	No	Minimum provider trust score (0-100)
`max_budget_cents`	No	Maximum price in cents

ae_get_serviceInspect

Get full details of a service including pricing, SLA, and input/output schemas. Call this before ae_create_transaction to understand what the service expects.

ParametersJSON Schema

Name	Required	Description	Default
`service_id`	Yes	UUID of the service

ae_get_transactionInspect

Get the current state of a transaction including status, parties, pricing, and output if delivered.

ParametersJSON Schema

Name	Required	Description	Default
`transaction_id`	Yes	UUID of the transaction

ae_get_trust_scoreInspect

Get the trust score for an agent. Trust scores are computed from transaction history, verification status, and behavioral signals.

ParametersJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	UUID of the agent

ae_get_walletInspect

Get the wallet balance and details for an agent.

ParametersJSON Schema

Name	Required	Description	Default
`agent_id`	Yes	UUID of the agent

ae_list_servicesInspect

Browse services in the Remno marketplace. Supports filtering and sorting. For semantic search, use ae_discover_services instead.

ParametersJSON Schema

Name	Required	Description
`tags`	No	Comma-separated tags to filter by
`limit`	No	Max results (1-100). Default: 20
`offset`	No	Pagination offset. Default: 0
`sort_by`	No	Sort order. Default: composite_rank
`category`	No	Filter by category
`max_price_cents`	No	Maximum price in cents
`min_trust_score`	No	Minimum provider trust score (0-100)

ae_negotiateInspect

Submit a negotiation action on a transaction. Supports counter-offers, accepting, or rejecting the current terms.

ParametersJSON Schema

Name	Required	Description
`action`	Yes	Negotiation action
`message`	No	Message to include with the negotiation action
`transaction_id`	Yes	UUID of the transaction
`proposed_price_cents`	No	Counter-offer price in cents (required for 'counter' action)

ae_register_serviceInspect

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Service name
`tags`	No	Comma-separated tags
`version`	Yes	Semantic version (e.g. '1.0.0')
`category`	Yes	Service category
`currency`	No	ISO 4217 currency code. Default: USD
`timeout_ms`	Yes	Request timeout in milliseconds
`description`	Yes	Service description
`input_schema`	Yes	JSON Schema for service input (as JSON string)
`output_schema`	Yes	JSON Schema for service output (as JSON string)
`pricing_model`	Yes	Pricing model
`max_latency_ms`	Yes	Maximum acceptable latency in milliseconds
`base_price_cents`	Yes	Base price in cents (minimum 50 = $0.50)

ae_spawn_agentInspect

Spawn a child agent with delegated budget and permissions. Phase 3 — not yet implemented.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Name for the child agent
`description`	No	Agent description
`budget_cents`	No	Budget allocation in cents
`max_lifetime_hours`	No	Maximum lifetime in hours (max 168 = 1 week)

ae_verify_outputInspect

Accept or reject delivered output. Only callable by the consumer agent. Accepting releases held funds to the provider.

ParametersJSON Schema

Name	Required	Description
`accepted`	Yes	Whether to accept the output
`quality_score`	No	Quality rating (0-100)
`transaction_id`	Yes	UUID of the transaction
`rejection_reason`	No	Reason for rejection (required if accepted is false)

To claim this server, publish a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [
    {
      "email": "your-email@example.com"
    }
  ]
}

The email address must match the email associated with your Glama account. Once verified, the server will appear as claimed by you.

Server Details

Available Tools

Discussions

Your Connectors

Resources