Fr Sirene

io.github.registry-deskPublished by GitHub account registry-deskv0.1.0Updated Oct 24, 2026

France Sirene company data (company-level, change tracking) for AI agents.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Lets an assistant look up French Sirene company records and track company-level changes through a hosted remote endpoint.

What you can do
This remote MCP server exposes France's Sirene company data to AI agents, described as company-level records with change tracking. It runs as a hosted streamable HTTP endpoint rather than a local package, so the assistant connects directly to the provider's service. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Use it when an assistant needs French company registry information, such as identifying companies or following changes to company records over time. It suits hosted setups where you prefer a remote endpoint over installing and maintaining a local server.
Requirements
A remote streamable HTTP endpoint; no local runtime or package is needed. Authentication is required: a bearer token sent in the Authorization header, described as an Apify API token in the form 'Bearer '. Network access to the provider's endpoint is required.
Before you install
The Authorization header carries an Apify API token, a secret that should be handled carefully. Each returned company is billed as one pay-per-event result on the caller's Apify account, so usage costs money and queries should be scoped deliberately. Company data is retrieved from a third-party hosted service.

Installation

In SourceWeft

  1. Open Fr Sirene in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/io.github.registry-desk%2Ffr-sirene/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": {
    "fr-sirene": {
      "type": "http",
      "url": "https://tormanliikenne--fr-sirene.apify.actor/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.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.