RobotScope MCP Server

net.robotscopePublished by robotscope.netOfficial publisherv0.1.0Updated Oct 24, 2026

Embodied AI & robotics MCP — 180+ companies, funding, Pulse, sector data (CC BY-NC 4.0)

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Provides an assistant with embodied AI and robotics sector data covering 180+ companies, funding, and Pulse signals.

What you can do
RobotScope is a remote MCP server for embodied AI and robotics sector intelligence. According to its registry description, it covers more than 180 companies along with funding information, a 'Pulse' signal, and other sector data. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when an assistant needs robotics or embodied AI market context, such as company lists, funding activity, or sector trend signals. It is less useful for general-purpose tasks outside that niche.
Requirements
It runs as a remote streamable HTTP endpoint, so no local runtime or package installation is needed. The manifest declares no authentication, environment variables, or headers, and no accounts or API keys are listed.
Before you install
The data is described as licensed CC BY-NC 4.0, which restricts commercial use and requires attribution, so check that your use fits the license. No tools are listed, so what the server can read or change cannot be verified from the manifest. Requests go to a third-party endpoint, so avoid sending sensitive data.

Installation

In SourceWeft

  1. Open RobotScope MCP Server in the dashboard and add it to a workspace.
  2. 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/net.robotscope%2Fmcp/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.

{
  "mcpServers": {
    "robotscope": {
      "type": "http",
      "url": "https://mcp.robotscope.net/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% 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

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

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

  • License10 pts

    Declare a license in the repository or the registry entry.