_ registry / mcp streamable-http · checked 2h ago

neuroencoder

https://api.neuroencoder.com

Registry code: 84951a74ec42e845

api record

EEG embeddings from EPI-300K: one 768-d vector per window (30 s by default, window_seconds 2 to 30). Without data: list_samples, get_sample. With a local .edf/.bdf/.npy file: create_upload, PUT the file to upload_url yourself, start_embedding_job, get_job until succeeded, then get_result_url (.npy float32 [windows, 768]). Sleep staging of a whole-night PSG: create_upload, PUT, start_sleep_staging_job, get_job, get_result_url (hypnogram JSON and CSV). Research use only; not a medical device.

endpoint
https://api.neuroencoder.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is neuroencoder live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is neuroencoder free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does neuroencoder have?
8 tools: account, get_sample, create_upload, start_embedding_job, start_sleep_staging_job, list_samples, get_job, get_result_url.
Is neuroencoder safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
554ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 8 tools
1 open2 auth-required 5 never probed 3 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_samples open 2h ago

    Precomputed real outputs (no upload needed): ids, titles, sizes, download URLs.

    mcp-tool

    {
      "type": "object",
      "title": "list_samplesArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_job auth-required 2h ago

    A job's status (queued, running, succeeded, failed, cancelled, expired), usage, error or result. Poll every 5 s while queued or running.

    mcp-tool

    {
      "type": "object",
      "title": "get_jobArguments",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "title": "Job Id"
        }
      }
    }
    arguments 13 lines
  • get_result_url auth-required 2h ago

    Fresh presigned GET URLs (10 minutes) of a succeeded job's result. Embeddings: .npy float32 [windows, 768], window i starts at i * t_start_step s. Sleep staging: url = hypnogram JSON (stage, probabilities, confidence per 30 s epoch), csv_url = CSV, plus the summary.

    mcp-tool

    {
      "type": "object",
      "title": "get_result_urlArguments",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "title": "Job Id"
        }
      }
    }
    arguments 13 lines
  • account unknown never probed

    This API key: tier, limits and usage this month.

    mcp-tool

    {
      "type": "object",
      "title": "accountArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_sample unknown never probed

    One sample: README, licence, channels_used, and its embeddings in the POST /v1/embeddings response format (first windows only for long ones).

    mcp-tool

    {
      "type": "object",
      "title": "get_sampleArguments",
      "required": [
        "name"
      ],
      "properties": {
        "name": {
          "type": "string",
          "title": "Name"
        }
      }
    }
    arguments 13 lines
  • create_upload unknown never probed

    Start an upload of a local .edf, .bdf or .npy file (at most 2 GB). Returns id and a presigned upload_url: PUT the file there within 10 minutes with exactly upload_headers (e.g. curl -X PUT --upload-file night.edf -H 'Content-Length: N' '<upload_url>', no Authorization header), then call start_embedding_job with the id. Only the extension of filename is used.

    mcp-tool

    {
      "type": "object",
      "title": "create_uploadArguments",
      "required": [
        "filename",
        "bytes"
      ],
      "properties": {
        "bytes": {
          "type": "integer",
          "title": "Bytes"
        },
        "filename": {
          "type": "string",
          "title": "Filename"
        }
      }
    }
    arguments 18 lines
  • start_embedding_job unknown never probed

    Queue an embeddings job on an uploaded file. window_seconds: 2 to 30 (default 30); stride_seconds: default window_seconds. picks: EDF/BDF channel labels to keep; channel_names: 10-20 labels overriding the file's; sfreq: required for .npy. Bills 30 s of EEG per window at any window_seconds (refunded on failure). Poll get_job.

    mcp-tool

    {
      "type": "object",
      "title": "start_embedding_jobArguments",
      "required": [
        "file_id"
      ],
      "properties": {
        "picks": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Picks",
          "default": null
        },
        "sfreq": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "null"
            }
          ],
          "title": "Sfreq",
          "default": null
        },
        "file_id": {
          "type": "string",
          "title": "File Id"
        },
        "channel_names": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Channel Names",
          "default": null
        },
        "stride_seconds": {
          "anyOf": [
            {
              "type": "number"
            },
            {
              "type": "null"
            }
          ],
          "title": "Stride Seconds",
          "default": null
        },
        "window_seconds": {
          "type": "number",
          "title": "Window Seconds",
          "default": 30
        }
      }
    }
    arguments 72 lines
  • start_sleep_staging_job unknown never probed

    Queue sleep staging of an uploaded whole-night PSG (.edf/.bdf; >= 1 EEG channel with a 10-20 label at >= 100 Hz; EOG used if present). eeg_channel/eog_channel: channels for the YASA features; picks, channel_names as for embeddings. Counts 1 night of the weekly quota (refunded on failure). Poll get_job, then get_result_url. Research use only, not a medical device.

    mcp-tool

    {
      "type": "object",
      "title": "start_sleep_staging_jobArguments",
      "required": [
        "file_id"
      ],
      "properties": {
        "picks": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Picks",
          "default": null
        },
        "units": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Units",
          "default": null
        },
        "file_id": {
          "type": "string",
          "title": "File Id"
        },
        "eeg_channel": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Eeg Channel",
          "default": null
        },
        "eog_channel": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Eog Channel",
          "default": null
        },
        "channel_names": {
          "anyOf": [
            {
              "type": "array",
              "items": {
                "type": "string"
              }
            },
            {
              "type": "null"
            }
          ],
          "title": "Channel Names",
          "default": null
        }
      }
    }
    arguments 79 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 84951a74ec42e845.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/84951a74ec42e845/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/84951a74ec42e845/badge.svg)](https://brick.blue/agent/84951a74ec42e845?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.