Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ai.fugentic/fugentic

REMOTE · FUGENTIC.MCP.FUGENTIC.AI

Fugentic helps any business to be found by customers using AI to find products and service.

0 this week 74 Trust /100

Last scanned (8 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 187 tokens (~31/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
  • 21 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 63. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Oct 26 +5
    • HTTPS: fail → unverified ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Schema quality: 28 → 31 ▼ functional
    • MCP protocol: fail → pass ▲ functional
    • Schema quality: excellent → good functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://fugentic.mcp.fugentic.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fugentic.ai CN=YE1,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 60cb63533e8b28f4f7d185e1597bac407df
SANs: *.fugentic.ai, *.mcp.fugentic.ai, fugentic.ai
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fugentic.mcp.fugentic.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
fugentic.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 400

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fugentic.mcp.fugentic.ai/mcp Verified 200
http (plaintext) http://fugentic.mcp.fugentic.ai/mcp Inconclusive 405
MCP tools · 6 exposed · ~170 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
about_fugentic ~39

What Fugentic is, who it is for, and what a business gets from it. Use when someone asks what Fugentic is or does.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_started ~21

How to sign up for Fugentic and what to have ready.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_it_works ~31

The steps a business goes through on Fugentic, from sign-up to a published, registered AI server.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plans ~17

Fugentic's plans and what each one includes.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

platform_modules ~21

The parts of the Fugentic platform and what each one does.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

what_ai_can_do_for_your_business ~41

What an AI assistant can do with a business's Fugentic AI server today, what we hope comes next, and the honest limits.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the ai.fugentic/fugentic MCP server?

ai.fugentic/fugentic is a hosted endpoint at https://fugentic.mcp.fugentic.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · fugentic.mcp.fugentic.ai

# add to Claude Code
claude mcp add --transport http ai-fugentic-fugentic 'https://fugentic.mcp.fugentic.ai/mcp'
Common questions

What is the ai.fugentic/fugentic MCP server?

ai.fugentic/fugentic is an MCP server listed in the public MCP registry as ai.fugentic/fugentic. Fugentic helps any business to be found by customers using AI to find products and service. This page covers its hosted endpoint (https://fugentic.mcp.fugentic.ai/mcp).

Is the ai.fugentic/fugentic MCP server safe to use?

ai.fugentic/fugentic scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ai.fugentic/fugentic MCP server expose?

ai.fugentic/fugentic exposes 6 tools: get_started, about_fugentic, how_it_works, platform_modules, what_ai_can_do_for_your_business, plans. Their descriptions and schemas cost roughly 170 tokens of context every time the server is loaded.

Does the ai.fugentic/fugentic MCP server require authentication?

Its publisher declares no required credentials for ai.fugentic/fugentic. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the ai.fugentic/fugentic MCP server still maintained?

ai.fugentic/fugentic is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.