
Kojiru Mcp
io.github.faulknerwayne73-droidPublished by GitHub account faulknerwayne73-droidv0.1.1Updated Oct 24, 2026
Kojiru Recourse Layer — agent credit primitives (ACS, stake, draw, anchor) live on Base mainnet
Overview
Kojiru's Recourse Layer exposes agent credit primitives — ACS, stake, draw and anchor — on Base mainnet to an AI assistant through a remote MCP endpoint.
- What you can do
- Work with agent credit primitives on Base mainnet: ACS, stake, draw and anchor, as described by the provider. Connect over a remote streamable HTTP endpoint, or run the published npm packages locally with the same transport. Authenticate each request with a bearer API key in the Authorization header. No individual tools are listed, so the exact operations available are not documented here.
- When to use it
- Consider it when you want an assistant to interact with Kojiru's on-chain agent credit primitives on Base mainnet, for example staking, drawing credit or anchoring records. It is not a general-purpose tool for other chains or unrelated tasks.
- Requirements
- A remote endpoint at the provider's Railway-hosted URL, or a local install of the kojiru-agentkit or kojiru-langchain npm packages. A bearer API key is required in the Authorization header; the provider says keys are requested through a contact form on its site. Network access to Base mainnet is implied.
Installation
In SourceWeft
- Open Kojiru Mcp in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.faulknerwayne73-droid%2Fkojiru-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"kojiru": {
"type": "http",
"url": "https://kojiru-platform-production.up.railway.app/mcp/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.