ApyHub Utility Tools (EU)

com.apyhubPublished by apyhub.comOfficial publisherv1.0.0Updated Oct 24, 2026

GDPR-compliant ApyHub utility APIs hosted in the EU. Requires an EU-generated ApyHub API key.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A remote MCP endpoint exposing ApyHub's EU-hosted, GDPR-compliant utility APIs to an assistant, authenticated with an EU-generated ApyHub API key.

What you can do
Connects an assistant to ApyHub's EU-hosted utility APIs through a single remote endpoint. The manifest lists no individual tools, so the exact set of utilities is not documented here. Access is authenticated with an ApyHub EU API key sent as a bearer token.
When to use it
Worth considering when you want an assistant to call ApyHub utility APIs and need EU-hosted, GDPR-compliant processing with an EU-generated key.
Requirements
A remote streamable HTTP endpoint; no local package or runtime. An ApyHub EU API key is required, sent in the Authorization header as a bearer token. OAuth authentication is declared as required.
Before you install
You must supply an ApyHub EU API key as a secret in the Authorization header; keep it private. Requests go to ApyHub's EU-hosted service, so data you send is processed by that third party. The manifest lists no tools, so review what the endpoint exposes before relying on it.

Installation

In SourceWeft

  1. Open ApyHub Utility Tools (EU) in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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-eu/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "apyhub-utility-tools-eu": {
      "type": "http",
      "url": "https://mcp.eu.apyhub.com/"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  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.

Other Apyhub integrations

ApyHub Utility Tools (US)

com.apyhubOfficial publisher

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.

Streamable HTTPWeb executableAuth
Developer ToolsCredential requiredOct 24, 2026