1. Conduid
  2. Cloud
  3. Widescreen Research
MCP server · Cloud

Widescreen Research

by · github.com/glassBead-tc/widescreen-research

bidirectional MCP server orchestrating an army of research drones on Cloud Run in GCP

Unclaimed MIT last commit 11 months ago cloud
InstallView source
51Fair

Scored 5 months ago · breakdown

About Widescreen Research

Widescreen Research is an MCP server published by glassBead-tc in the Cloud category: bidirectional MCP server orchestrating an army of research drones on Cloud Run in GCP.

The repository has 6 stars and 1 forks, with the last commit 11 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/glassBead-tc/widescreen-research

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Ask AI

✦

Ask AI about Widescreen Research

Powered by Claude · Grounded in docs

I know everything about Widescreen Research. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 3 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • ✓License declaredUsable under a stated license.
  • ✓Tests presentA test suite exists in the repository.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

1 check has not been run yet.

README

widescreen-research

Go CI

Bidirectional MCP server orchestrating an army of research drones on Cloud Run in GCP.

Repo status

  • Primary implementation: Go (coordinator and drone)
  • Examples: Node (under examples/node)

Clone

git clone https://github.com/glassBead-tc/widescreen-research.git
cd widescreen-research

Quickstart (Go)

go version  # require 1.23+
go mod download

# terminal 1
LOG_LEVEL=debug go run ./cmd/coordinator

# terminal 2
DRONE_TYPE=research EXA_API_KEY=your-local-only-key LOG_LEVEL=debug go run ./cmd/drone

Open http://localhost:8080 and GET /health.

Docker (Go)

docker build -t widescreen/coordinator:dev .
docker run --rm -p 8080:8080 widescreen/coordinator:dev

Deploy to Cloud Run (Go)

Preferred: inject secrets from Secret Manager. Example:

gcloud run deploy widescreen-coordinator \
  --source . \
  --region=us-central1 \
  --allow-unauthenticated \
  --set-env-vars=LOG_LEVEL=info \
  --set-secrets=EXA_API_KEY=exa_api_key:latest

Node examples (optional)

The Node projects live under ./examples/node/ and are provided as examples only.

  • Requires Node 18+ LTS
  • See each example's README for usage

Architecture and design

See project_spec.md for the canonical architecture, roles, and protocols.

Directory layout

  • cmd/coordinator: Go coordinator service (binary)
  • cmd/drone: Go drone worker (binary)
  • pkg/...: Reusable Go packages
  • examples/node/...: Node example MCP servers and templates

Operations

  • Endpoints: GET / (info), GET /health (readiness)
  • Logging: structured logs; control via LOG_LEVEL
  • Recommended: enable OpenTelemetry to Cloud Monitoring (future work)

Contributing

See CONTRIBUTING.md (coming soon). Please run go fmt/go vet and tests locally before submitting PRs.

README fetched from the repository 3 days ago. The original is authoritative.

Questions

About Widescreen Research

How do I install Widescreen Research?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Widescreen Research safe to use with an AI agent?

Its trust score is 51 out of 100 (fair). It passes 4 of the 5 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Widescreen Research still maintained?

The last commit was 11 months ago and 5 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.