FoFa MCP Server

Created By
help116114a year ago
This server provides access to FoFa API functionality through the Model Context Protocol.
Overview

what is FoFa MCP Server?

FoFa MCP Server is a Model Context Protocol (MCP) server that provides access to FoFa API functionality, allowing AI assistants to query information about internet-connected devices and services.

how to use FoFa MCP Server?

To use FoFa MCP Server, clone the repository, install dependencies, set up your FoFa API key and email, and start the server. You can also integrate it with MCP-compatible AI assistants like Claude.

key features of FoFa MCP Server?

  • Search Capabilities: Search FoFa's database for devices and services based on various queries.
  • User Information: Retrieve user information from FoFa, including account details and usage statistics.

use cases of FoFa MCP Server?

  1. Querying information about internet-connected devices for security assessments.
  2. Integrating with AI assistants to enhance their capabilities in retrieving device information.
  3. Automating the process of gathering data from FoFa for research purposes.

FAQ from FoFa MCP Server?

  • What is required to run FoFa MCP Server?

You need Node.js (version 16 or higher), npm, and a valid FoFa API key and email.

  • Can I integrate FoFa MCP Server with other AI assistants?

Yes! FoFa MCP Server can be integrated with any MCP-compatible AI assistant.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
help116114
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago