Fido

ai.fetchfidoPublished by fetchfido.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Scheduling built for sign language interpreting: assignments, availability, Suggestions, exports.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Fido is a remote MCP server for sign language interpreting scheduling, letting an assistant work with assignments, availability, Suggestions and exports.

What you can do
Work with interpreting assignments and scheduling data through the connected service, as described for sign language interpreting workflows. Check and manage interpreter availability. Use Suggestions to support scheduling decisions. Produce exports of scheduling information. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Relevant for teams or coordinators who schedule sign language interpreters and want an assistant to help with assignments, availability, suggestions and exports inside that workflow.
Requirements
A remote MCP endpoint reached over streamable HTTP at the provider's hosted address. OAuth authentication is required, so a Fido account and an OAuth sign-in are needed. No environment variables or headers are declared.
Before you install
The server requires OAuth sign-in, granting it access to your Fido account data. Scheduling actions may create, change or remove assignments and availability, and exports may move scheduling data outside the service. Tool-level permissions are not documented, so review what the assistant is allowed to do before connecting.

Installation

In SourceWeft

  1. Open Fido 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/ai.fetchfido%2Ffido/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": {
    "fido": {
      "type": "http",
      "url": "https://mcp.fetchfido.ai/mcp"
    }
  }
}

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.0LatestOct 23, 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.