Cred
Wire agentic payment capabilities into your stack via Cred’s MCP remote instead of custom payment orchestration code.
Overview
fyi.cred/cred is a MCP server for the Build phase that exposes agentic payment capabilities to coding agents.
What is this MCP server?
- Agentic payments focus per cred.fyi positioning
- Streamable-http MCP remote at https://mcp.cred.fyi/mcp
- Early server version 0.0.1 for evolving payment tool surface
- Fits payment-aware coding agents in standard MCP clients
- Server version 0.0.1 in published metadata
- Single streamable-http remote endpoint
What problem does it solve?
You need agents to pay or settle without hand-rolling every payment API and secret management path in your repo.
Who is it for?
Indie builders prototyping paid agent actions, API usage billing, or machine payments inside MCP-first workflows.
Skip if: Teams that need full merchant onboarding UI, detailed public tool docs, or non-agent traditional checkout only.
What do I get? / Deliverables
Your agent gains Cred-backed payment tools through one MCP remote once credentials and client config are in place.
- Registered Cred MCP remote in the agent environment
- Agent workflows that invoke payment tools instead of hard-coded charge scripts
Recommended MCP Servers
Journey fit
How it compares
Payments MCP remote, not a local SKILL.md playbook or accounting export skill.
Common Questions / FAQ
Who is fyi.cred/cred for?
Developers shipping agent products who want a cred.fyi-backed MCP integration for agentic payments rather than bespoke SDK glue.
When should I use fyi.cred/cred?
Use it during build integrations when payment steps should be invokable as MCP tools from your coding agent.
How do I add fyi.cred/cred to my agent?
Configure the streamable-http remote https://mcp.cred.fyi/mcp in your MCP client and follow cred.fyi for API keys or account setup.