
Stargate Mcp
io.github.junct-botPublished by GitHub account junct-botv1.1.0Updated Oct 24, 2026
Stargate - 42 tools for cross-chain transfers and bridge data
Overview
A hosted, no-auth MCP endpoint exposing 42 Stargate tools for cross-chain transfers and bridge data to an AI assistant.
- What you can do
- Query Stargate bridge and cross-chain transfer data through tools mapped one-to-one to real Stargate API endpoints, as described by the provider (the tool list itself is not published). The server is generated from the Stargate API specification, so each tool corresponds to an actual endpoint rather than an invented one. It is aimed at agents working with DeFi and crypto bridging information.
- When to use it
- Use it when an assistant needs Stargate bridge or cross-chain transfer data and you want a hosted endpoint with no setup or credentials. It suits crypto and DeFi research or agent workflows rather than general-purpose tasks.
- Requirements
- A remote Streamable HTTP endpoint at the provider's hosted address; no local runtime, API key or authentication is required according to the README. Network access to the endpoint is needed.
Installation
In SourceWeft
- Open Stargate Mcp in the dashboard and add it to a workspace.
- 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.junct-bot%2Fstargate-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": {
"stargate": {
"type": "http",
"url": "https://stargate.mcp.junct.dev/mcp"
}
}
}README
Stargate MCP Server
MCP server for Stargate. Agent-ready API for Stargate.
Hosted at stargate.mcp.junct.dev/mcp. Free to use. No auth. No API key required.
Part of Junct — the agent-readiness layer for the crypto stack.
Quick Start
Add to your MCP client config (Claude Desktop, Cursor, Windsurf):
About
This MCP server is deterministically generated from the Stargate API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
- Protocol: Stargate
- Endpoint:
https://stargate.mcp.junct.dev/mcp - Transport: Streamable HTTP
- Auth: None required
- Documentation: stargate.mcp.junct.dev/llms.txt
- Server card: stargate.mcp.junct.dev/.well-known/mcp/server.json
Links
Keywords
Stargate, MCP server, DeFi, AI agent, agent-ready API, crypto tools, Model Context Protocol, hosted MCP
Source: README.md at commit ad1abfe
Tools
0Version history
1- v1.1.0LatestSep 16, 2026
Score
40% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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
- License10 pts
Declare a license in the repository or the registry entry.