Ask Gina MCP server
2026년 11월 2일 커밋AI 클라이언트가 암호화폐 토큰, Hyperliquid perps, Polymarket 마켓 및 사용자 계정에 대해 읽기 전용 조사를 수행할 수 있도록 지원합니다.
다른 이름 askgina/plugins, plugins
- 스타
- 4
- Tools
- —
- 다운로드, 30일
- —
- 최신 버전
- 1.0.0
- 마지막 커밋
- 2026년 11월 2일
- 라이선스
- Apache-2.0
Ask Gina MCP란?
Ask Gina은(는) MCP server입니다. AI 클라이언트가 암호화폐 토큰, Hyperliquid perps, Polymarket 마켓 및 사용자 계정에 대해 읽기 전용 조사를 수행할 수 있도록 지원합니다.
프로젝트 README에서 생성된 요약
Ask Gina MCP server 정보
Ask Gina는 AI 클라이언트가 다양한 암호화폐 및 예측 마켓에 대해 읽기 전용 조사를 수행할 수 있는 특화된 인터페이스를 제공합니다. 에이전트가 암호화폐 토큰, Hyperliquid perps, Polymarket 마켓 및 특정 사용자 계정을 조사할 수 있도록 지원합니다. 이 도구는 프로그래밍 방식의 인터페이스를 통해 실시간 시장 데이터를 AI 워크플로우에 통합하려는 개발자와 연구자를 위해 설계되었습니다.
사용자는 필요한 tools:read 권한이 있는 외부 발급 Gina bearer token을 제공하여 서비스에 연결합니다. 서버가 로그인이나 OAuth 인증을 직접 처리하지 않으므로 클라이언트가 필요한 자격 증명을 직접 제공해야 합니다. Cursor, Devin, Grok Bot, Antigravity, ChatGPT, Claude를 포함한 여러 인기 AI 호스트 및 클라이언트와 호환됩니다. 시스템은 TypeScript SDK와 Bun CLI를 사용하여 구축되어 데이터 검색 작업에서 높은 성능을 보장합니다.
프로젝트의 README를 바탕으로 작성되었습니다. 모든 활용 사례는 해당 내용의 인용문과 대조하여 확인합니다.
Ask Gina MCP 설치 방법
형식 확인: 2026년 11월 10일Cursor에 추가Goose에 추가Claude Code에 Ask Gina MCP 설치
$ claude mcp add --transport http plugins https://askgina.ai/ai/gina/mcpCursor에 Ask Gina MCP 설치
~/.cursor/mcp.json
{
"mcpServers": {
"plugins": {
"url": "https://askgina.ai/ai/gina/mcp"
}
}
}VS Code에 Ask Gina MCP 설치
.vscode/mcp.json
{
"servers": {
"plugins": {
"type": "http",
"url": "https://askgina.ai/ai/gina/mcp"
}
}
}VS Code CLI에 Ask Gina MCP 설치
$ code --add-mcp '{"name":"plugins","type":"http","url":"https://askgina.ai/ai/gina/mcp"}'Codex에 Ask Gina MCP 설치
$ codex mcp add plugins --url https://askgina.ai/ai/gina/mcpCodex config.toml에 Ask Gina MCP 설치
~/.codex/config.toml
[mcp_servers.plugins] url = "https://askgina.ai/ai/gina/mcp"
Gemini CLI에 Ask Gina MCP 설치
$ gemini mcp add -s user --transport http plugins https://askgina.ai/ai/gina/mcpGemini settings.json에 Ask Gina MCP 설치
~/.gemini/settings.json
{
"mcpServers": {
"plugins": {
"url": "https://askgina.ai/ai/gina/mcp",
"type": "http"
}
}
}자동 검사
2026년 11월 14일에 실행됨전체 보고서 →아직 인증되지 않았습니다. 서버는 80점 이상의 점수, 심각한 결함 없음, 그리고 검사에 충분한 데이터를 갖추어야 합니다. 검사 방식 · 점수를 높이기 위해 수정할 항목
- 소스 저장소 연결 및 접근 가능askgina/plugins is public and reachablegithub.com/askgina/plugins ↗통과
- 패키지가 이 저장소를 소스로 명시검사되지 않음
- 빌드 출처(Sigstore 증명)검사되지 않음
- 오픈 소스 라이선스 (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗통과
- 최근 1년 내 커밋 또는 릴리스Last commit or release 2026-11-02github.com/askgina/plugins ↗통과
- OpenSSF Scorecard검사되지 않음
- 패키지 이름이 인기 패키지와 유사하지 않음검사되지 않음
- 패키지 및 해당 종속성에 중요한 보안 권고 없음검사되지 않음
- 모델에 대한 숨겨진 지침 없음0 tool descriptions and the README read; no override phrases, credential paths or hidden characters통과
- 파괴적인 도구에 라벨 표시됨검사되지 않음
- 원격 엔드포인트가 MCP 핸드셰이크에 응답Endpoint did not answer initialize: HTTP 404결함 발견
README
GitHub에서 보기askgina/plugins
What this is: the Apache-2.0 workspace for the Ask Gina programmatic client (a TypeScript SDK and a Bun CLI), the listed plugin (a portable core plus host adapters), the evals that check whether models use that plugin correctly, and the public evals app. It does not log you in: SDK and CLI callers bring their own token (see below).
Production Gina MCP is at https://askgina.ai/ai/gina/mcp. SDK and CLI callers
supply an externally acquired Gina bearer token with tools:read; neither client
implements login or OAuth authentication. See
authentication and
Agent Setup to obtain a read-only token.
New here? Start with Start here, which routes you by goal. The Reference below it is for people changing the build, the evals app, or the lint setup.
Start here
Pick your goal
| I want to... | Go to |
|---|---|
| Call Gina from TypeScript code | packages/sdk/README.md |
| Call Gina from a terminal | packages/cli/README.md |
| Use the shared catalog and protocol types | packages/contracts/README.md |
| Install the plugin in a host (Antigravity, Cursor, Grok Bot, Devin, and others) | plugins/ask-gina/README.md |
| Connect ChatGPT, Claude, Codex, or another client | Public Connect guides |
| Run or change the evals | packages/evals/README.md. Start with replay: it makes no network calls and needs no secrets. |
| Work on the public evals app | Public evals app in Reference |
| Contribute a change | ai_docs/contributing.md, then the loop below |
| Edit the public docs site | docs/ is the Mintlify source; authoring rules are in ai_docs/docs/authoring.md |
Antigravity installs local plugin directories with agy plugin install. The
Antigravity connect guide covers
research, Spot, Perps and Predictions, their OAuth scopes, and confirmation for
venue writes. This source-install route does not imply a Marketplace listing.
Contributor loop
You need Bun 1.4.x (the root packageManager is bun@1.4.0). From the
repository root:
bun install --frozen-lockfile
bun run fmt:check
bun run lint
bun run check
bun run test
bun run check:target-conformance
bun run artifacts
bun run verify:artifacts
bun run check:public-boundary
This is the list ai_docs/contributing.md asks you
to run before proposing a change. Pull-request CI runs these and a few more
gates (see What CI runs in Reference). main has no protected
required checks, so CI does not gate merge or publish packages.
Things that surprise people:
- Edit skills in one place. Canonical skill source lives only under
plugins/ask-gina/skills/. Host skill trees are generated at pack time and must not be committed. bun run checkis more than lint. It also runsevals:check-public,evals:check-grading, the TypeScript compiler, and the TypeScript import check.- Docs changes have their own checks. If you touch
docs/ortools/docs/, also runbun run docs:testandbun run docs:check. Releasing a user-facing feature adds the steps inai_docs/release-docs-checklist.md. - Fix Effect diagnostics at the source. Don't suppress them or add
baselines. The one exception is
nodeBuiltinImporton the two synchronous SHA-256 helpers (packages/contracts/src/sha256.tsandpackages/evals/src/canonical-json.ts): EffectCryptois asynchronous, and schema filters and streamed file hashes need a synchronous digest. Importsha256Hexfrom those helpers instead ofnode:crypto.
Map of the repository
| Path | What lives there |
|---|---|
packages/contracts |
@askgina/contracts: public catalog, protocol literals, receipt schemas. |
packages/sdk |
@askgina/sdk: TypeScript client. |
packages/cli |
@askgina/cli: the compiled ask-gina Bun binary. |
packages/evals |
@askgina/evals: replay, live runners, grading, sanitization, public export. |
plugins/ask-gina |
@askgina/plugin-core: canonical plugin inputs (manifest, skills, eval cases, targets) and the Devin install notes. |
apps/evals |
The public evals React/Vite app and its Storybook. Not an npm-published package. |
tools/ |
Build, pack, verify, and boundary-check scripts; eval regrade and public-artifact checks; docs check. |
docs/ |
Public Mintlify docs source. |
ai_docs/ |
Internal engineering docs: contributing, architecture, security, eval handoffs, docs authoring. |
patches/ |
Dependency patches, including the two Storybook docgen compatibility patches. |
scripts/ |
Helper that applies the Effect TSGo patch. |
specs/ |
Design plans. |
Reference
Packages and runtimes
@askgina/contracts: public catalog, protocol literals, and receipt schemas; root-only ESM for Node >=24 and Bun >=1.4@askgina/sdk: TypeScript client; root-only ESM for Node >=24 and Bun >=1.4@askgina/cli: compiled Bunask-ginabinary; Bun 1.4.x only@askgina/plugin-core: host-specific plugin core and loaders, inplugins/ask-gina@askgina/evals: compiled hermetic/live eval tools, shared contracts, adapters, replay, grading, and sanitization; Bun 1.4.x only
The contracts and SDK packages have no CommonJS, browser, edge, or subpath entrypoints.
Commands
Root scripts from package.json, grouped by purpose:
# Setup and quality
bun install --frozen-lockfile
bun run audit
bun run fmt:check
bun run lint
bun run check # quality: evals:check-public, evals:check-grading, vp check, tsc, check:typescript-imports
bun run typecheck
bun run test
bun run check:typescript-imports
bun run check:target-conformance
bun run effect-tsgo:diagnostics
# Packaging and verification
bun run build
bun run artifacts
bun run verify:artifacts
bun run verify:packages
bun run verify:targets
bun run smoke:install
bun run check:public-boundary
bun run check:marketplace:codex
# Public evals app
bun run evals:dev # Vite dev server (default port 5173)
bun run evals:build
bun run evals:typecheck
bun run evals:check-public
bun run evals:check-grading
bun run storybook # Storybook on port 6006
bun run build-storybook
# Evals
bun run eval:replay
bun run eval:responses
bun run eval:codex
bun run eval:openrouter
bun run eval:claude
bun run eval:omp
bun run eval:export-public
# Docs
bun run docs:check
bun run docs:test
What CI runs
Pull-request CI (.github/workflows/ci.yml) runs, in order:
bun install --frozen-lockfile
bun run audit
bun run fmt:check
bun run lint
bun run check
bun run evals:typecheck
bun run evals:build
bun run build-storybook
bun run test
bun run check:target-conformance
bun run artifacts
bun run verify:artifacts
bun run smoke:install
bun run check:public-boundary
It then smokes the Codex marketplace with a pinned Codex CLI at the published
revision. The docs workflow (.github/workflows/docs.yml) runs on pull requests
that touch docs/, tools/docs/, the plugin skills or .mcp.json, or the
contracts entry point: it runs the docs check, skills catalog and sweep comparison
tests (bun run docs:test) and node tools/docs/check.mjs --external.
Public evals app
apps/evals is the public React/Vite app (not an npm-published package) with the Ask Gina
landing-page typography, watercolor artwork, UI components, and Storybook. It has a leaderboard, model
profiles, task evidence explorer, and methodology page. Measured September reports
coexist with explicitly illustrative fixtures. Measured rows cover tool conformance,
not final-answer correctness; public downloads are reviewed projections, not full
conversation archives. The viewer makes no live tool or wallet calls.
CI also runs evals:build and build-storybook. Their outputs stay in
apps/evals/dist/app and apps/evals/dist/storybook, separate from published
package artifacts. Storybook uses the existing TypeScript 7 toolchain plus a
TypeScript 5 compiler-API alias and the two docgen compatibility patches under
patches/. Local fonts and artwork are pinned in tools/public-source-assets.ts.
Before bundling, the public-artifact gate checks historical Claude reports against strict projection fields and an exact reviewed path/hash allowlist. Changed or new Claude JSON requires privacy review and corresponding provenance/allowlist updates; never update a hash merely to admit raw provider output. Full conversations remain outside the public repository. Sanitizing current files does not remove historical Git objects, fork-network copies, or previous deployment/cache contents.
Lint configuration
@shadcn/lint is registered in the root vite.config.ts.
apps/evals/src enables shadcn/no-raw-colors,
shadcn/no-arbitrary-values with allow: ["layout"],
shadcn/no-restyle with allow: ["layout"] plus named evals CSS hooks on
primitives, and shadcn/require-static-classes.
apps/evals/src/components/ui turns no-arbitrary-values, no-restyle, and
require-static-classes off so primitives can keep structural values and
internal variants. bun run lint checks the whole workspace, and
bun run check includes lint. Add further rules under lint.rules, spreading
effectTsgoRecommended.rules first, or in app-scoped lint.overrides. See the
available rules and
configuration examples.
Artifacts
bun run artifacts builds the five package outputs with vp pack; the
custom packer then creates five package tarballs, six complete host archives, one
four-skill candidate archive, and contract, package, target, and eval receipts
under ignored dist/. bun run verify:artifacts performs clean
tarball installs and runtime checks. Nothing here publishes, releases, deploys,
submits, or calls production during pull-request CI.
Eval runners
Live eval runners are bun run eval:responses, eval:codex, eval:openrouter,
eval:claude, and eval:omp; hermetic replay is eval:replay. Credentials,
flags, what each runner can and cannot prove, capture, and publication rules
are in packages/evals/README.md.
One detail the evals README does not name: OpenRouter's --server-url accepts
exactly https://askgina.ai/ai/gina/mcp (the default) or
https://alpha.askgina.ai/ai/gina/mcp. Any other URL, trailing slashes, and
venue MCP endpoints are rejected. OMP native mode's synthetic stored-credential
smoke is not a real OAuth or subscription authentication test.
Ask Gina MCP 질문
Ask Gina MCP를 Claude Code에 추가하려면 어떻게 하나요?
터미널에서 claude mcp add --transport http plugins https://askgina.ai/ai/gina/mcp를 실행합니다. 모든 프로젝트에서 사용할 수 있게 하려면 --scope user를 추가합니다.
Ask Gina MCP를 Cursor에 추가하려면 어떻게 하나요?
~/.cursor/mcp.json를 열고 mcpServers 아래에 서버를 추가합니다. 위 설치 섹션에 표시된 Cursor 구성을 사용합니다.
Ask Gina 인증은 어떻게 하나요?
사용자는 tools:read 권한이 포함된 외부에서 발급받은 Gina bearer token을 제공해야 합니다. 이 MCP server는 자체적인 로그인 또는 OAuth 흐름을 구현하지 않습니다.