Rpcs1 Sdk — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Rpcs1 Sdk (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- mcp-name: io.github.travisbergen2/rpcs1-agent-tuner -->
Diagnose whether deployed AI agents are matched to their operating environment.
A configuration framework for AI agents that translates environmental characteristics (entropy, stakes, predictability) into specific LLM parameter recommendations — grounded in RPCS-1 receiver dynamics.
rpcs1-sdk/
├── packages/core/ # TypeScript recommendation engine (@rpcs1/core)
├── sdk/python/ # Python SDK (pip install rpcs1)
└── .github/workflows/ # CI/CDpip install rpcs1from rpcs1 import recommend_params
config = recommend_params(
task_description="Customer support agent",
environment_entropy="dynamic",
environment_predictability="somewhat_predictable",
stakes="high",
target_platform="anthropic",
)
print(config.platform_parameters.temperature) # e.g. 0.52
print(config.predicted_regime) # 'stable'
print(config.reasoning) # cites Matching Principleimport { recommend } from '@rpcs1/core';
const rec = recommend({
task: { task_summary: 'Customer support agent' },
environment: {
entropy: 'dynamic',
predictability: 'somewhat_predictable',
stakes: 'high',
context_relevance: 'medium',
commitment_style: 'cautious',
},
target_platform: 'anthropic',
});
console.log(rec.platform_parameters.temperature);
console.log(rec.predicted_regime);# Install dependencies
npm ci --include=optional
# Build and test TypeScript core
npm run build --workspace=@rpcs1/core
npm run test --workspace=@rpcs1/core
# Test Python SDK
cd sdk/python
pip install -e ".[dev]"
pytest -vThe SDK implements Pred-09-5 from IMM Paper 9:
Stable receivers in an environment with entropy H satisfy TI ~ 1/H.
High-entropy environments → short attention windows (TI ~ 10). Low-entropy environments → long attention windows (TI ~ 90).
Every parameter recommendation traces back to this principle or the basin stability geometry (oscillation/overload/freeze boundary conditions).
Interactive tuner: https://rpcs1.dev
RPCS-1 is also available as a public, anonymous, read-only MCP server:
https://rpcs1.dev/mcpIt exposes one focused tool:
recommend_agent_configuration — use when designing, tuning, or diagnosing an AI agentagainst environmental entropy, predictability, stakes, context horizon, and commitment style.
Connection details and client compatibility notes are available at https://rpcs1.dev/docs/mcp. Practical coding, support, and research examples are available at https://rpcs1.dev/docs/examples.
Hyperagent uses the fixed public OAuth client hyperagent-rpcs1 with PKCE and the registered callback https://hyperagent.com/api/mcp-servers/callback. No client secret is required.
The MCP surface intentionally wraps the existing deterministic recommendation engine. Broader communication, market, and decision-analysis tools should be added only after their scoring contracts are implemented and tested in the core package.
Discovery metadata:
server.jsonProduction controls:
MCP_HOURLY_LIMIT controls per-instance MCP throttling (default: 120 requests per IP/hour).MCP_MAX_BODY_BYTES limits request bodies (default: 65536 bytes).MCP_ALLOWED_HOSTS is a comma-separated production host allowlist.MCP_OAUTH_JWT_SECRET signs short-lived OAuth authorization codes and access tokens./api/health reports deployment and MCP readiness metadata.For globally consistent abuse protection across Vercel instances, configure a Vercel Firewall rate-limit rule for /mcp. The in-process limiter is defense in depth, not a distributed quota.
Glama Docker checks should build and launch the local STDIO server, not connect to the hosted https://rpcs1.dev/mcp endpoint. Use this build spec:
{
"buildSteps": [
"npm ci --include=optional",
"npm run build --workspace=@rpcs1/core",
"npm run build --workspace=@rpcs1/mcp-server"
],
"cmdArguments": [
"mcp-proxy",
"--",
"node",
"packages/mcp-server/dist/index.js"
],
"environmentVariablesJsonSchema": {
"type": "object",
"properties": {},
"required": []
},
"placeholderArguments": {}
}MIT
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.