ApyHub Utility Tools (US)
com.apyhubPublished by apyhub.comOfficial publisherv1.0.0Updated Oct 24, 2026
1,500+ ApyHub utility APIs served from the US cluster. Requires a US-generated ApyHub API key.
The publisher's own server: ApyHub Utility Tools (EU)
Overview
A remote MCP endpoint exposing ApyHub's 1,500+ utility APIs from its US cluster, letting an assistant call those utilities with a US-issued ApyHub API key.
- What you can do
- Connect an assistant to ApyHub's US-hosted utility API collection, covering over 1,500 utility APIs across many small tasks. The manifest lists no individual tools, so the exact operations available depend on the ApyHub catalog rather than a fixed tool list. Access is authenticated with an ApyHub API key sent as a bearer token.
- When to use it
- Useful when you already work with ApyHub utilities and want an assistant to reach them directly from the US cluster, or when you need a US-generated ApyHub key to be honored.
- Requirements
- A remote streamable HTTP endpoint at mcp.us.apyhub.com; no local package or runtime. OAuth authentication is required, and requests carry an Authorization header with a bearer ApyHub US API key. The key must be generated for the US region.
Installation
In SourceWeft
- Open ApyHub Utility Tools (US) in the dashboard and add it to a workspace.
- Connect the required 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/com.apyhub%2Fmcp-server-us/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. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"apyhub-utility-tools-us": {
"type": "http",
"url": "https://mcp.us.apyhub.com/"
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
67% 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.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.