Manufact

Back to submission

fiber-core

mcp.fiber.ai/mcp

Protocol: MCP 2025-11-25
Server version: 3.2.0
Supports: Tools
Resources
Prompts
Logging

Overall score

Last reviewed at Oct 15, 2026, 00:36:08 UTC

Server metadata

4 of 8 fields50/1004 / 8 pts

Identity, discovery, and usage metadata advertised during the MCP handshake.

Stable server name

fiber-core

10/10Source

Human-readable title

Add a human-readable title for clients and directories.

0/10Source

Useful description

Describe what the server helps an agent do.

0/20Source

Server version

Version 3.2.0

10/10Source

Public website

Link to a public website or documentation page.

0/10Source

Scalable or high-resolution icon

Advertise a vector or at least 128px server icon.

0/10Source

Server instructions

Usage instructions provided for agents.

20/20Source

Declared capabilities

Supports Tools, Resources, Prompts, Logging.

10/10Source

Extensions

io.modelcontextprotocol/ui

Server instructions

Fiber AI API - Discovery and execution tools. HOW TO USE (3 steps): 1. search_endpoints("your intent", constraints=[...], preferredTags=[...], tagPack="...") - Choose the best operations with ranked alternatives 2. get_endpoint_details_full("operationId") - Get complete schema and examples for complex fields 3. call_operation("operationId", {body: {...}}) - Execute EXAMPLES: - "find companies" → search_endpoints("find AI companies in SF", constraints=["country", "headcount"]) → companySearch - "get email" → search_endpoints("reveal work email for known profile") → syncContactEnrichment - "find people" → search_endpoints("find VP engineering in fintech") → peopleSearch AUTHENTICATION: Every API call requires an apiKey parameter. Ask the user for their Fiber API key (starts with sk_live_ or sk_test_) and include it in every call_operation request body. FOR COMPLEX WORKFLOWS (bulk operations, audiences): Read llms://fiber.ai/llms.txt for step-by-step guidance. For API choice among similar operations, read llms://fiber.ai/api-selector.

Protocol

Pass100/10016 / 16 pts

Connection, authentication, and protocol compatibility.

MCP negotiation succeeds (v1/v2)

MCP legacy negotiation succeeded in 1226ms

Source

Tools list returns results

5 tool(s) returned

Source

Resources list responds

3 resource(s) returned

Source

Server declares tools capability

Server declares tools capability in initialize response

Source

Tools

Issues93/10022.3 / 24 pts

Tool definitions, annotations, and client compatibility.

All tools have descriptions

All tools have non-empty descriptions

Skills over MCP resources are readable

Server does not advertise the Skills over MCP extension

Claude Code metadata fits its 2 KB fields

Tool descriptions and server instructions fit Claude Code's 2 KB fields

Source

All tools have OpenAI behavior hints

4 behavior annotation issue(s) found

How to fix: On each tool, declare annotations.readOnlyHint, annotations.destructiveHint, and annotations.openWorldHint as booleans. The policy review separately assesses whether their values match the tool's actual behavior.

errorChatGPT

Source

Tool names use valid characters

All tool names use valid characters

Source

Claude tools declare applicable behavior hints

All tools include an applicable readOnlyHint or destructiveHint

Source

All tools have a display title

Source

Claude tool names are within 64 characters

All tool names are within Claude's 64-character limit

Source

Cursor tool-name budget advisory

No tool name independently exhausts Cursor's observed 60-character combined budget

Observed behavior

Tool names follow the MCP 1–128 character range

All tool names follow the MCP recommended length

Source

Tool input header annotations are valid

All x-mcp-header annotations satisfy Streamable HTTP requirements

Source

Tool names follow MCP uniqueness guidance

All tool names are unique

Source

ChatGPT tool names are unique

All tool names are unique

Source

Declared output schemas have a valid basic structure

5 declared output schema(s) pass basic structural validation; schemas may describe any JSON value, including arrays

Source

Tool input schemas have a valid object structure

All tool input schemas have a valid object structure

Source

OpenAI file parameters use valid schemas

All declared OpenAI file parameters use reviewer-valid schemas

Source

Tool text has no hidden control characters

No invisible or control characters found in tool-facing text

Source

MCP Apps

Skipped-0 / 20 pts

App resources, metadata, and rendering requirements.

View resource envelope is valid

No view resources found — view checks skipped

All discovered view resources were inspected

No view resources found — view checks skipped

Source

Tool invocation metadata present

No view resources found — view checks skipped

Source

Tool visibility metadata is valid

No view resources found — view checks skipped

Source

Tool-linked resource URI is readable

No view resources found — view checks skipped

Source

CSP metadata covers literal external origins

No view resources found — view checks skipped

Source

View resources declare a domain

No view resources found — view checks skipped

Source

Declared domains respond

No view resources found — view checks skipped

View resource metadata complete

No view resources found — view checks skipped

Source

Tool documentation quality

5 tools reviewed61/10019.5 / 32 pts

How clearly each tool’s title, description, input and output schemas, and behavior annotations guide an agent.

search_endpointsTitles 100Descriptions 77Inputs 0Annotations 75Outputs 555/100

Title100/100

Search Endpoints

The title clearly communicates the tool’s action and subject. Keep it concise.

Description77/100

Canonical API selection tool for endpoint discovery and ranking. Use this first to get the top recommended operations for a user intent. Supports optional constraints plus tag-scoped selection via preferredTags, excludedTags, or a curated tagPack key.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Not provided

Missing description. Explain what this value means and how to supply it.

constraints

Not provided

Missing description. Explain what this value means and how to supply it.

preferredTags

Not provided

Missing description. Explain what this value means and how to supply it.

excludedTags

Not provided

Missing description. Explain what this value means and how to supply it.

tagPack

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare destructiveHint based on the tool’s actual behavior.

{
  "title": "Search Endpoints",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true
}

Output schema5/100

Declare the result fields and their types in the output schema.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "search_endpoints",
  "title": "Search Endpoints",
  "description": "Canonical API selection tool for endpoint discovery and ranking.\n\nUse this first to get the top recommended operations for a user intent.\nSupports optional constraints plus tag-scoped selection via preferredTags,\nexcludedTags, or a curated tagPack key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "query": {
        "type": "string"
      },
      "tagPack": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "constraints": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "excludedTags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "preferredTags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "Search Endpoints",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  }
}

list_tag_packsTitles 99Descriptions 65Inputs 100Annotations 75Outputs 578/100

Title99/100

List Tag Packs

The title clearly communicates the tool’s action and subject. Keep it concise.

Description65/100

List curated tag packs for large tool catalogs. Use this to narrow exploration (for example social-media or enrichment).

Describe the returned information so the agent knows whether it will answer the request.

Inputs100/100

This tool declares no inputs, so argument descriptions are not needed.

No input fields.

Annotations75/100

Declare destructiveHint based on the tool’s actual behavior.

{
  "title": "List Tag Packs",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true
}

Output schema5/100

Declare the result fields and their types in the output schema.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "list_tag_packs",
  "title": "List Tag Packs",
  "description": "List curated tag packs for large tool catalogs.\n\nUse this to narrow exploration (for example social-media or enrichment).",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "List Tag Packs",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  }
}

list_all_endpointsTitles 100Descriptions 69Inputs 0Annotations 75Outputs 553/100

Title100/100

List All Endpoints

The title clearly communicates the tool’s action and subject. Keep it concise.

Description69/100

List available Fiber API endpoints with optional tag/search filtering.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

Annotations75/100

Declare destructiveHint based on the tool’s actual behavior.

{
  "title": "List All Endpoints",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true
}

Output schema5/100

Declare the result fields and their types in the output schema.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "list_all_endpoints",
  "title": "List All Endpoints",
  "description": "List available Fiber API endpoints with optional tag/search filtering.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "tags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "search": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "tagPack": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "List All Endpoints",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  }
}

get_endpoint_details_fullTitles 97Descriptions 96Inputs 0Annotations 75Outputs 760/100

Title97/100

Get Endpoint Details

The title clearly communicates the tool’s action and subject. Keep it concise.

Description96/100

Get COMPLETE schema and details for a specific API operation. Use this BEFORE calling an API to understand exactly what parameters are needed. Args: operationId: The operation ID (e.g., "syncContactEnrichment") Returns: Complete schema including all required/optional fields, request body schema, response schema, and example usage.

The description explains the capability, when to use it, and what to expect.

Inputs0/100

0 of 1 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

operationId

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare destructiveHint based on the tool’s actual behavior.

{
  "title": "Get Endpoint Details",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true
}

Output schema7/100

Declare the result fields and their types in the output schema.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "get_endpoint_details_full",
  "title": "Get Endpoint Details",
  "description": "Get COMPLETE schema and details for a specific API operation.\n\nUse this BEFORE calling an API to understand exactly what parameters are needed.\n\nArgs:\n    operationId: The operation ID (e.g., \"syncContactEnrichment\")\n\nReturns:\n    Complete schema including all required/optional fields, request body schema,\n    response schema, and example usage.",
  "inputSchema": {
    "type": "object",
    "required": [
      "operationId"
    ],
    "properties": {
      "operationId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "Get Endpoint Details",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  }
}

call_operationTitles 80Descriptions 91Inputs 0Annotations 100Outputs 2058/100

Title80/100

Call Operation

The title clearly communicates the tool’s action and subject. Keep it concise.

Description91/100

Execute any Fiber API operation by operationId. IMPORTANT: - Most operations require `apiKey` in the request body. - Prefer search_endpoints() first when operation choice is ambiguous. - Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes. Args: operationId: The operation ID to call params: Parameters dict: {"body": {...}, "path": {...}, "query": {...}} Returns: API response data or error details.

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 2 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

operationId

Not provided

Missing description. Explain what this value means and how to supply it.

params

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations100/100

All four behavior hints are declared.

{
  "title": "Call Operation",
  "readOnlyHint": false,
  "openWorldHint": true,
  "idempotentHint": false,
  "destructiveHint": false
}

Output schema20/100

Describe the returned fields so an agent can interpret the result.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "call_operation",
  "title": "Call Operation",
  "description": "Execute any Fiber API operation by operationId.\n\nIMPORTANT:\n- Most operations require `apiKey` in the request body.\n- Prefer search_endpoints() first when operation choice is ambiguous.\n- Use get_endpoint_details_full(operationId='...') first for complex/nested parameter shapes.\n\nArgs:\n    operationId: The operation ID to call\n    params: Parameters dict: {\"body\": {...}, \"path\": {...}, \"query\": {...}}\n\nReturns:\n    API response data or error details.",
  "inputSchema": {
    "type": "object",
    "required": [
      "operationId"
    ],
    "properties": {
      "params": {
        "anyOf": [
          {
            "type": "object",
            "additionalProperties": true
          },
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "operationId": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "Call Operation",
    "readOnlyHint": false,
    "openWorldHint": true,
    "idempotentHint": false,
    "destructiveHint": false
  }
}

Put your MCP to the test

A few tasks worth trying with this server, chosen from its reviewed tools. These have not been run.

01List all endpointsList available Fiber API endpoints with optional tag/search filtering.
02Search EndpointsCanonical API selection tool for endpoint discovery and ranking.
03Get Endpoint DetailsGet COMPLETE schema and details for a specific API operation.
04List Tag PacksList curated tag packs for large tool catalogs.

Want to run these tasks against your MCP server with us?

Test your MCP in Cloud Book a test call

Overview

Category: Developer tools

FAQ

fiber-core setup, tools, quality score, publishing readiness, and alternatives.

How do I add fiber-core to Claude, ChatGPT, or Cursor?

Add fiber-core to Claude, ChatGPT, or Cursor by connecting its remote MCP URL in each client's MCP settings. In Claude, add a custom connector. In ChatGPT, add an MCP app. In Cursor, add an MCP server under Settings. The MCP URL is https://mcp.fiber.ai/mcp.

Is fiber-core MCP ready for ChatGPT and Claude?

As of October 15, 2026, fiber-core scores 94/100 on Manufact's MCP publishing checklist. The scan does not yet meet ChatGPT publishing checks and meets Claude publishing checks. Passing these checks does not guarantee marketplace approval.

How clear is fiber-core's MCP tool documentation?

As of October 15, 2026, fiber-core scores 61/100 in Manufact's review of tool titles, descriptions, input and output schemas, and behavior annotations. The review covers 5 of 5 discovered tools. The quality score measures documentation clarity; runtime behavior and marketplace readiness require separate checks.

What are the best alternatives to fiber-core?

As of October 15, 2026, alternatives to fiber-core in developer-tools on the Manufact MCP catalog include Held at the Gate, AgentMail, Celesto Cloud Computers, GitCafe, and Manufact Cloud.

How can fiber-core improve its MCP documentation?

list_all_endpoints is the lowest-scoring reviewed tool at 53/100. 0 of 4 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values. Open its review for feedback and a copyable fix prompt, then rerun the documentation review after updating your tool metadata.

Not your MCP?

Review any public or OAuth MCP server for protocol compatibility, tool documentation, and ChatGPT and Claude publishing readiness. No account required.

Get your MCP score

Back to leaderboard

Opening your score report…

Title100/100

Search Endpoints

The title clearly communicates the tool’s action and subject. Keep it concise.

Description77/100

Describe the returned information so the agent knows whether it will answer the request.

Inputs0/100

0 of 6 inputs have descriptions. Add descriptions to the missing inputs, including where to obtain IDs and how to supply values.

query

Not provided

Missing description. Explain what this value means and how to supply it.

constraints

Not provided

Missing description. Explain what this value means and how to supply it.

preferredTags

Not provided

Missing description. Explain what this value means and how to supply it.

excludedTags

Not provided

Missing description. Explain what this value means and how to supply it.

tagPack

Not provided

Missing description. Explain what this value means and how to supply it.

limit

Not provided

Missing description. Explain what this value means and how to supply it.

Annotations75/100

Declare destructiveHint based on the tool’s actual behavior.

{
  "title": "Search Endpoints",
  "readOnlyHint": true,
  "openWorldHint": true,
  "idempotentHint": true
}

Output schema5/100

Declare the result fields and their types in the output schema.

View output schema

{
  "type": "object",
  "additionalProperties": true
}

Original tool metadata

{
  "name": "search_endpoints",
  "title": "Search Endpoints",
  "description": "Canonical API selection tool for endpoint discovery and ranking.\n\nUse this first to get the top recommended operations for a user intent.\nSupports optional constraints plus tag-scoped selection via preferredTags,\nexcludedTags, or a curated tagPack key.",
  "inputSchema": {
    "type": "object",
    "required": [
      "query"
    ],
    "properties": {
      "limit": {
        "anyOf": [
          {
            "type": "integer"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "query": {
        "type": "string"
      },
      "tagPack": {
        "anyOf": [
          {
            "type": "string"
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "constraints": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "excludedTags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      },
      "preferredTags": {
        "anyOf": [
          {
            "type": "array",
            "items": {
              "type": "string"
            }
          },
          {
            "type": "null"
          }
        ],
        "default": null
      }
    },
    "additionalProperties": false
  },
  "outputSchema": {
    "type": "object",
    "additionalProperties": true
  },
  "annotations": {
    "title": "Search Endpoints",
    "readOnlyHint": true,
    "openWorldHint": true,
    "idempotentHint": true
  }
}

Manufact

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title100/100

Description77/100

Inputs0/100

Annotations75/100

Output schema5/100

Title99/100

Description65/100

Inputs100/100

Annotations75/100

Output schema5/100

Title100/100

Description69/100

Inputs0/100

Annotations75/100

Output schema5/100

Title97/100

Description96/100

Inputs0/100

Annotations75/100

Output schema7/100

Title80/100

Description91/100

Inputs0/100

Annotations100/100

Output schema20/100

Put your MCP to the test

Overview

Related MCP servers

FAQ

Not your MCP?

Server metadata

Protocol

Tools

MCP Apps

Tool documentation quality

Title100/100

Description77/100

Inputs0/100

Annotations75/100

Output schema5/100

Title99/100

Description65/100

Inputs100/100

Annotations75/100

Output schema5/100

Title100/100

Description69/100

Inputs0/100

Annotations75/100

Output schema5/100

Title97/100

Description96/100

Inputs0/100

Annotations75/100

Output schema7/100

Title80/100

Description91/100

Inputs0/100

Annotations100/100

Output schema20/100

Put your MCP to the test

Overview

Related MCP servers

FAQ

Not your MCP?