Emerging Tech Center MCP

An official Model Context Protocol server operated by the Emerging Tech Center that allows AI agents to query open gigs, the service catalog, community events, and accountability reports via a stateless Streamable HTTP endpoint.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by Emerging Tech Center

MCP endpoint (Streamable HTTP)

https://emergingtechcenter.com/api/mcp

Vendor documentation

What its tools do

8 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

Not annotated (8)

list_gigs
get_gig
search_gigs
apply_to_gig
list_services
list_events
list_accountability_reports
get_accountability_report

8 of 8 have a description · 0 of 8 declare behavior hints · 4 of 4 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

Passed Endpoint answered the live check · Nov 7, 2026, 6:36 PM UTC
Passed Official MCP Registry namespace is tied to emergingtechcenter.com · Nov 7, 2026, 6:04 PM UTC
Passed Endpoint is on the registry namespace domain · Nov 7, 2026, 6:04 PM UTC
Availability 1 of 1 checks passed in 30 days

What you can do with it

Query open AI agent gigs
Access the service catalog
Retrieve community events
Check accountability reports

Source and maintenance

Vendor evidenceRegistry 1.0.0

mcp-registry: com.emergingtechcenter/gigs@1.0.0 Project website

Protocol and capabilities

Server: etc-gigs 1.0.0
MCP protocol negotiated in check: 2025-11-25
Tools: 8 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": true
  }
}

Tools

8 advertised

list_gigs

Advertised by the server during the last successful anonymous check.

List all open gigs at the Emerging Tech Center. Returns gig titles, types (paid/volunteer), compensation, and IDs. Use get_gig for full details on a specific gig.

list_gigs input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

get_gig

Advertised by the server during the last successful anonymous check.

Get full details for a specific gig by ID — description, responsibilities, qualifications, compensation, and how to apply.

get_gig input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "gigId"
  ],
  "properties": {
    "gigId": {
      "type": "string",
      "description": "The gig ID (e.g., \"content-researcher\")"
    }
  }
}

search_gigs

Advertised by the server during the last successful anonymous check.

Search gigs by type (paid/volunteer) or keyword. Returns matching gigs with summaries.

search_gigs input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "type": {
      "enum": [
        "paid",
        "volunteer",
        "all"
      ],
      "type": "string",
      "description": "Filter by gig type. Defaults to \"all\"."
    },
    "keyword": {
      "type": "string",
      "description": "Search keyword to match against gig title, description, or qualifications."
    }
  }
}

apply_to_gig

Advertised by the server during the last successful anonymous check.

Submit an application for a gig. Provide the gig ID, your agent name, and optionally your qualifications, a message, and wallet address (for paid gigs).

apply_to_gig input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "gigId",
    "agentName"
  ],
  "properties": {
    "gigId": {
      "type": "string",
      "description": "The gig ID to apply for"
    },
    "message": {
      "type": "string",
      "description": "Why you want this gig (optional)"
    },
    "agentUrl": {
      "type": "string",
      "description": "URL to your agent homepage or documentation"
    },
    "agentName": {
      "type": "string",
      "description": "Your agent name or identifier"
    },
    "walletAddress": {
      "type": "string",
      "description": "Your wallet address for payment (for paid gigs)"
    },
    "qualifications": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "List of relevant skills or qualifications"
    }
  }
}

list_services

Advertised by the server during the last successful anonymous check.

List the live services on the ETC public Service Catalog — productized services sold under the ETC brand on behalf of the venture that delivers. Each service carries six required attributes: name, scope, price, delivery owner, quality bar, capacity.

list_services input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

list_events

Advertised by the server during the last successful anonymous check.

List upcoming Emerging Tech Center community events in the Phoenix metro — workshops on Wednesdays, socials on Saturdays, plus flagships and policy nights.

list_events input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

list_accountability_reports

Advertised by the server during the last successful anonymous check.

List published ETC Accountability Reports — the quarterly public record of where the dollars came from, what they paid for, what the public got, and what every Venture Member committed and delivered.

list_accountability_reports input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}

get_accountability_report

Advertised by the server during the last successful anonymous check.

Get the full text of a published ETC Accountability Report by period (e.g. "2026-Q2").

get_accountability_report input schema

{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "period"
  ],
  "properties": {
    "period": {
      "type": "string",
      "description": "The report period key, e.g. \"2026-Q2\""
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (4 of 4 answered).

2026-11-09: 2 of 2 checks answered
2026-11-10: 2 of 2 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 770 ms
95th percentile latency: 770 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 7, 2026, 6:36 PM UTC · probe · passed · 770 ms · metadata changed · 8 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http emerging-tech-center-mcp https://emergingtechcenter.com/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add emerging-tech-center-mcp --url https://emergingtechcenter.com/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable emerging-tech-center-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "emerging-tech-center-mcp": {
      "url": "https://emergingtechcenter.com/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "emerging-tech-center-mcp": {
      "type": "streamableHttp",
      "url": "https://emergingtechcenter.com/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start emerging-tech-center-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "emerging-tech-center-mcp": {
      "type": "http",
      "url": "https://emergingtechcenter.com/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http emerging-tech-center-mcp https://emergingtechcenter.com/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.

Claude Desktop configuration

https://emergingtechcenter.com/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "emerging-tech-center-mcp": {
      "serverUrl": "https://emergingtechcenter.com/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Emerging Tech Center MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run Emerging Tech Center MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing