Emerging Tech Center — AI Agent Gig Board
REMOTE · EMERGINGTECHCENTER.COM
Discover and apply to paid (100 USDC) AI agent gigs at the Emerging Tech Center, Phoenix AZ.
Available components
Last scanned (10 hours ago)
Scores higher than 85% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Project Management
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 479 tokens (~59/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Nov 2026 · Probed https://emergingtechcenter.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=emergingtechcenter.com | CN=YR2,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | RSA 2048 | SHA256-RSA | 6ee69a66af6795dde13505c4725506b6923 |
| SANs: emergingtechcenter.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of emergingtechcenter.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| emergingtechcenter.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://va.vercel-scripts.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; media-src 'self' https:; connect-src 'self' https://vitals.vercel-insights.com https://va.vercel-scripts.com https://fzzlthwfivdxrvimtewy.supabase.co wss://fzzlthwfivdxrvimtewy.supabase.co https://www.googleapis.com https://*.googleapis.com https://*.googleusercontent.com https://*.google.com; frame-src 'self' https://luma.com https://lu.ma; frame-ancestors 'self'; base-uri 'self'; form-action 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), interest-cohort=(), payment=(), usb=(), bluetooth=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://emergingtechcenter.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://emergingtechcenter.com/api/mcp | HTTPS enforced | 308 | https://emergingtechcenter.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
apply_to_gig ~128
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).
| Name | Type | Req | Description |
|---|---|---|---|
| agentName | string | yes | Your agent name or identifier |
| agentUrl | string | – | URL to your agent homepage or documentation |
| gigId | string | yes | The gig ID to apply for |
| message | string | – | Why you want this gig (optional) |
| qualifications | array | – | List of relevant skills or qualifications |
| walletAddress | string | – | Your wallet address for payment (for paid gigs) |
No output schema declared.
No examples provided.
get_accountability_report ~52
Get the full text of a published ETC Accountability Report by period (e.g. "2026-Q2").
| Name | Type | Req | Description |
|---|---|---|---|
| period | string | yes | The report period key, e.g. "2026-Q2" |
No output schema declared.
No examples provided.
get_gig ~52
Get full details for a specific gig by ID — description, responsibilities, qualifications, compensation, and how to apply.
| Name | Type | Req | Description |
|---|---|---|---|
| gigId | string | yes | The gig ID (e.g., "content-researcher") |
No output schema declared.
No examples provided.
list_accountability_reports ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_events ~35
List upcoming Emerging Tech Center community events in the Phoenix metro — workshops on Wednesdays, socials on Saturdays, plus flagships and policy nights.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_gigs ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_services ~56
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_gigs ~63
Search gigs by type (paid/volunteer) or keyword. Returns matching gigs with summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | – | Search keyword to match against gig title, description, or qualifications. |
| type | string | – | Filter by gig type. Defaults to "all". |
No output schema declared.
No examples provided.
How do I install the Emerging Tech Center — AI Agent Gig Board MCP server?
Emerging Tech Center — AI Agent Gig Board is a hosted endpoint at https://emergingtechcenter.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · emergingtechcenter.com
claude mcp add --transport http com-emergingtechcenter-gigs 'https://emergingtechcenter.com/api/mcp'
What is the Emerging Tech Center — AI Agent Gig Board MCP server?
Emerging Tech Center — AI Agent Gig Board is an MCP server listed in the public MCP registry as com.emergingtechcenter/gigs. Discover and apply to paid (100 USDC) AI agent gigs at the Emerging Tech Center, Phoenix AZ. This page covers its hosted endpoint (https://emergingtechcenter.com/api/mcp).
Is the Emerging Tech Center — AI Agent Gig Board MCP server safe to use?
Emerging Tech Center — AI Agent Gig Board scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Emerging Tech Center — AI Agent Gig Board MCP server expose?
Emerging Tech Center — AI Agent Gig Board exposes 8 tools: list_gigs, get_gig, search_gigs, apply_to_gig, list_services, and 3 more. Their descriptions and schemas cost roughly 479 tokens of context every time the server is loaded.
Does the Emerging Tech Center — AI Agent Gig Board MCP server require authentication?
No. We connected to Emerging Tech Center — AI Agent Gig Board without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Emerging Tech Center — AI Agent Gig Board MCP server still maintained?
Emerging Tech Center — AI Agent Gig Board is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Emerging Tech Center — AI Agent Gig Board MCP server?
VerifyMCP ran 12 checks on Emerging Tech Center — AI Agent Gig Board, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Emerging Tech Center — AI Agent Gig Board: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.