RPCS-1

MCP Integration

RPCS-1 provides a public Streamable HTTP MCP server for agent configuration recommendations. The server is anonymous, deterministic, read-only, and idempotent. It does not require an API key, account, or OAuth authentication.

Connection details

  • Name: RPCS1 Agent Tuner
  • URL: https://rpcs1.dev/mcp
  • Transport: Streamable HTTP
  • Authentication: None

Hyperagent compatibility

RPCS-1 provides a fixed public OAuth client for Hyperagent using authorization code flow with PKCE. In Hyperagent, enable Bring my own OAuth app and enter:

  • Redirect URI: https://hyperagent.com/api/mcp-servers/callback
  • Client ID: hyperagent-rpcs1
  • Client secret: leave blank
  • Authorization endpoint: https://rpcs1.dev/oauth/authorize
  • Token endpoint: https://rpcs1.dev/oauth/token
  • Scopes: mcp:tools

RPCS-1 also publishes OAuth discovery metadata, so the endpoint fields may be left blank when Hyperagent successfully discovers them automatically.

Available tool

The server exposes one focused tool: recommend_agent_configuration. Use it when designing, tuning, or diagnosing an AI agent against environmental entropy, predictability, stakes, context horizon, and commitment style.

Safety and privacy

The MCP tool returns recommendations without modifying external systems. Only send task and environment information you are comfortable submitting to the RPCS-1 service. Recommendations support engineering decisions but do not replace domain-specific safety, legal, medical, or financial review.